Device, method, and graphical user interface for editing screenshot images

ABSTRACT

An electronic device: displays a first portion of content within an application interface; detects a screenshot capture input; and, in response to detecting the screenshot capture input: captures a screenshot image of the first portion of the content; and displays a screenshot editing interface that includes the screenshot image of the first portion of the content within an image area and expansion affordances provided to expand the screenshot image. The electronic device also: while displaying the screenshot editing interface, detects an expansion input that corresponds to expanding the screenshot image in one or more dimensions; and, in response to detecting the expansion input, modifies the screenshot image by displaying a second portion of the content within the image area in addition to the first portion of the content, where the second portion of the content was not displayed before detecting the screenshot capture input.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/945,556, filed on Jul. 31, 2020, which claims priority to U.S. patentapplication Ser. No. 15/978,115, filed on May 12, 2018, and U.S.Provisional Patent Application No. 62/506,682, filed on May 16, 2017,which are incorporated herein by reference in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that enable screenshot image editing.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Example touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Example manipulations include adjusting the position and/or size of oneor more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Example user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture, iPhoto, Photos fromApple Inc. of Cupertino, Calif.), a digital content (e.g., videos andmusic) management application (e.g., iTunes from Apple Inc. ofCupertino, Calif.), a drawing application, a presentation application(e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But methods for performing these manipulations are cumbersome andinefficient. For example, using a sequence of mouse based inputs toselect one or more user interface objects and perform one or moreactions on the selected user interface objects is tedious and creates asignificant cognitive burden on a user. In addition, these methods takelonger than necessary, thereby wasting energy. This latter considerationis particularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for editing screenshot images. Suchmethods and interfaces optionally complement or replace conventionalmethods for editing screenshot images. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methods andinterfaces conserve power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch-screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through stylus and/or fingercontacts and gestures on the touch-sensitive surface. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer readable storagemedium or other computer program product configured for execution by oneor more processors.

In accordance with some embodiments, a method is performed at a devicewith one or more processors, non-transitory memory, a display, and oneor more input devices. The method includes: while displaying content onthe display, detecting, via the one or more input devices, a screenshotcapture input; and, in response to detecting the screenshot captureinput: capturing a screenshot image of the content displayed on thedisplay; and displaying, on the display, a thumbnail representation ofthe screenshot image overlaid on the content displayed on the displayand captured within the screenshot image. The method also includes:detecting, via the one or more input devices, a respective inputdirected to the thumbnail representation of the screenshot image; and,in response to detecting the respective input directed to the thumbnailrepresentation of the screenshot image, and in accordance with adetermination that the respective input corresponds to a selectioninput, displaying, on the display, a screenshot editing interfaceprovided to edit the screenshot image, where the screenshot editinginterface includes the screenshot image.

In accordance with some embodiments, a method is performed at a devicewith one or more processors, non-transitory memory, a display, and oneor more input devices. The method includes: displaying, on the display,a first sub-portion of content within an application interface; whiledisplaying the first sub-portion of the content, detecting, via the oneor more input devices, a screenshot capture input; and, in response todetecting the screenshot capture input: capturing a screenshot image ofthe first sub-portion of the content within the application interface;and displaying, on the display, a screenshot editing interface providedto edit the screenshot image, where the screenshot editing interfaceincludes the screenshot image of the first sub-portion of the contentwithin an image area and one or more expansion affordances provided toexpand the screenshot image in a corresponding direction. The methodalso includes: while displaying the screenshot editing interface,detecting, via the one or more input devices, an expansion input thatcorresponds to expanding the screenshot image in one or more dimensions;and, in response to detecting the expansion input, modifying thescreenshot image by displaying a second sub-portion of the contentwithin the image area in addition to the first sub-portion of thecontent, where the second sub-portion of the content was not displayedwithin the application interface before detecting the screenshot captureinput.

In accordance with some embodiments, an electronic device includes adisplay, one or more input devices, one or more processors,non-transitory memory, and one or more programs; the one or moreprograms are stored in the non-transitory memory and configured to beexecuted by the one or more processors and the one or more programsinclude instructions for performing or causing performance of theoperations of any of the methods described herein. In accordance withsome embodiments, a non-transitory computer readable storage medium hasstored therein instructions which when executed by one or moreprocessors of an electronic device with a display and one or more inputdevices, cause the device to perform or cause performance of theoperations of any of the methods described herein. In accordance withsome embodiments, a graphical user interface on an electronic devicewith a display, one or more input devices, a non-transitory memory, andone or more processors configured to execute one or more programs storedin the non-transitory memory, including one or more of the elementsdisplayed in any of the methods described above, which are updated inresponse to inputs, as described in any of the methods described herein.In accordance with some embodiments, an electronic device includes: adisplay, one or more input devices; and means for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, an information processing apparatus,for use in an electronic device with a display and one or more inputdevices, includes means for performing or causing performance of theoperations of any of the methods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface are provided with faster, more efficient methodsand interfaces for editing screenshot images, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor editing screenshot images.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an example user interface for a menu of applicationson a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIGS. 5A-5CC illustrate example user interfaces for editing a screenshotimage in accordance with some embodiments.

FIGS. 6A-6N illustrate example user interfaces for expanding ascreenshot image in accordance with some embodiments.

FIGS. 7A-7E illustrate a flow diagram of a method of editing ascreenshot image interface in accordance with some embodiments.

FIGS. 8A-8C illustrate a flow diagram of a method of expanding ascreenshot image within a screenshot editing interface in accordancewith some embodiments.

DESCRIPTION OF EMBODIMENTS

Typically, performing a screenshot operation is an unintuitive,non-user-friendly experience. Furthermore, screenshot images aretypically saved to a background clipboard unbeknownst to anunsophisticated user. Accordingly, in embodiments described below, afterperforming a screenshot capture input, a thumbnail representation of thescreenshot image is displayed over the current application interface inorder to provide a visual cue indicating that the screenshot captureinput was successful. Additionally, in embodiments described below, ascreenshot editing interface is displayed in order to provide a seamlessuser experience that requires less time and user inputs when modifyingscreenshot images. This also reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

Saving and/or sharing a lengthy text message thread or a web page thatspans multiple scroll operations can be a cumbersome experience.Accordingly, in embodiments described below, after performing ascreenshot capture input, the screenshot editing interface provides aseamless and intuitive user experience that requires less time and userinputs when expanding screenshot images. This also reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

Below, FIGS. 1A-1B, 2-3, and 4A-4B provide a description of exampledevices. FIGS. 7A-7E illustrate a flow diagram of a method of editing ascreenshot image. The user interfaces in FIGS. 5A-5CC are used toillustrate the process in FIGS. 7A-7E. FIGS. 8A-8C illustrate a flowdiagram of a method of expanding a screenshot image. The user interfacesin FIGS. 6A-6N are used to illustrate the process in FIGS. 8A-8C.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 163 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an example embodiment, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an example embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch-sensitive display system 112 or an extension of thetouch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 163 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver for obtaining information concerning the location ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3. Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 163 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   contacts module 137 (sometimes called an address book or contact    list);-   telephone module 138;-   video conferencing module 139;-   e-mail client module 140;-   instant messaging (IM) module 141;-   workout support module 142;-   camera module 143 for still and/or video images;-   image management module 144;-   browser module 147;-   calendar module 148;-   widget modules 149, which optionally include one or more of: weather    widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm    clock widget 149-4, dictionary widget 149-5, and other widgets    obtained by the user, as well as user-created widgets 149-6;-   widget creator module 150 for making user-created widgets 149-6;-   search module 151;-   video and music player module 152, which is, optionally, made up of    a video player module and a music player module;-   notes module 153;-   map module 154; and/or-   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and video andmusic player module 152, workout support module 142 includes executableinstructions to create workouts (e.g., with time, distance, and/orcalorie burning goals); communicate with workout sensors (in sportsdevices and smart watches); receive workout sensor data; calibratesensors used to monitor a workout; select and play music for a workout;and display, store and transmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipherals interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In some embodiments includingactive event recognizer determination module 173, event dispatchermodule 174 delivers the event information to an event recognizerdetermined by active event recognizer determination module 173. In someembodiments, event dispatcher module 174 stores in an event queue theevent information, which is retrieved by a respective event receivermodule 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher-level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events ina respective event, such as event 1 (187-1) or event 2 (187-2) include,for example, touch begin, touch end, touch movement, touch cancellation,and multiple touching. In one example, the definition for event 1(187-1) is a double tap on a displayed object. The double tap, forexample, comprises a first touch (touch begin) on the displayed objectfor a predetermined phase, a first lift-off (touch end) for apredetermined phase, a second touch (touch begin) on the displayedobject for a predetermined phase, and a second lift-off (touch end) fora predetermined phase. In another example, the definition for event 2(187-2) is a dragging on a displayed object. The dragging, for example,comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, the event definition of a respective event, such asevent 1 (187-1) or event 2 (187-2), includes a definition of an eventfor a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event, such asevent 1 (187-1) or event 2 (187-2) also includes delayed actions thatdelay delivery of the event information until after it has beendetermined whether the sequence of sub-events does or does notcorrespond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 112,164, 165, 166, 167, 168, and 169 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   Signal strength indicator(s) 402 for wireless communication(s), such    as cellular and Wi-Fi signals;-   Time 404;-   Bluetooth indicator 405;-   Battery status indicator 406;-   Tray 408 with icons for frequently used applications, such as:    -   Icon 416 for telephone module 138, labeled “Phone,” which        optionally includes an indicator 414 of the number of missed        calls or voicemail messages;    -   Icon 418 for e-mail client module 140, labeled “Mail,” which        optionally includes an indicator 410 of the number of unread        e-mails;    -   Icon 420 for browser module 147, labeled “Browser”; and    -   Icon 422 for video and music player module 152, also referred to        as iPod (trademark of Apple Inc.) module 152, labeled “iPod”;        and-   Icons for other applications, such as:    -   Icon 424 for IM module 141, labeled “Text”;    -   Icon 426 for calendar module 148, labeled “Calendar”;    -   Icon 428 for image management module 144, labeled “Photos”;    -   Icon 430 for camera module 143, labeled “Camera”;    -   Icon 432 for online video module 155, labeled “Online Video”;    -   Icon 434 for stocks widget 149-2, labeled “Stocks”;    -   Icon 436 for map module 154, labeled “Map”;    -   Icon 438 for weather widget 149-1, labeled “Weather”;    -   Icon 440 for alarm clock widget 169-6, labeled “Clock”;    -   Icon 442 for workout support module 142, labeled “Workout        Support”;    -   Icon 444 for notes module 153, labeled “Notes”; and    -   Icon 446 for a settings application or module, which provides        access to settings for device 100 and its various applications        136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, in some embodiments, icon 422 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Device 300also, optionally, includes one or more contact intensity sensors (e.g.,one or more of sensors 359) for detecting intensity of contacts ontouch-sensitive surface 451 and/or one or more tactile output generators359 for generating tactile outputs for a user of device 300.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 inFIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to aprimary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). Inaccordance with these embodiments, the device detects contacts (e.g.,460 and 462 in FIG. 4B) with the touch-sensitive surface 451 atlocations that correspond to respective locations on the display (e.g.,in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In thisway, user inputs (e.g., contacts 460 and 462, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 451 in FIG.4B) are used by the device to manipulate the user interface on thedisplay (e.g., 450 in FIG. 4B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

User Interfaces and Associated Processes

Attention is now directed toward embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as a portable multifunction device (PMD) 100 with adisplay, a touch-sensitive surface, and optionally one or more sensorsto detect intensity of contacts with the touch-sensitive surface, or adevice 300 with one or more processors, non-transitory memory, adisplay, and one or more input devices.

FIGS. 5A-5CC illustrate example user interfaces for editing a screenshotimage within a screenshot editing interface in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the process in FIGS. 7A-7E.Although some of the examples which follow will be given with referenceto inputs on a touch-screen display (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface 451 that is separate from thedisplay 450, as shown in FIG. 4B.

FIG. 5A illustrates displaying a web browser interface 502 associatedwith a web browser application executed by the device 100. As shown inFIG. 5A, the web browser interface 502 includes: a content region 504associated with a web page, an address bar 506 displaying a URL (e.g.,caesar.org/the_gallic_wars) for the web page, a refresh affordance 508,and a toolbar region with a plurality of affordances 510A, 510B, 512A,512B, and 512C.

According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 510A (e.g., the backaffordance), the device 100 updates the web browser interface 502 todisplay a previous web page. According to some embodiments, in responseto activation (e.g., selection with a contact) of the affordance 510B(e.g., the next affordance), the device 100 updates the web browserinterface 502 to display a next web page.

According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 512A (e.g., the shareaffordance), the device 100 displays a transport interface overlaid onthe web browser interface 502 provided to share the web page via one ormore communication means, such as email, SMS, etc., and/or to performone of a plurality of operations on the web page such as a copyoperation, a print operation, etc. (e.g., similar to the transportinterface 570 in FIG. 5L and the transport interface 650 in FIG. 6B).According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 512B (e.g., the bookmarkaffordance), the device 100 replaces display of the web browserinterface 502 with a bookmark management interface for viewing and/ormodifying bookmarked web pages, favorited web pages, and/or a savedreading list of web pages. According to some embodiments, in response toactivation (e.g., selection with a contact) of the affordance 512C(e.g., the tabs affordance), the device 100 replaces display of the webbrowser interface 502 with a tab management interface for viewing and/ormodifying web browser tabs.

FIGS. 5A-5D show a sequence in which a thumbnail representation of ascreenshot image is overlaid on the web browser interface. For example,the device 100 detects a screenshot capture input such as a predefinedgesture, voice command, key combination (e.g., print screen key,power+home button combination, etc.), and/or the like. FIG. 5Billustrates displaying a thumbnail representation 514A of a screenshotimage 534 in a first state (e.g., a first opacity and/or sharpness levelor a first fade-in state) overlaid on the web browser interface 502 inresponse to detecting the screenshot capture input. For example, thescreenshot image 534 corresponds to the web browser interface 502displayed in FIG. 5A. For example, the screenshot image 534 is shrunk togenerate the thumbnail representation 514A based on predefineddimensions, a predefined aspect ratio, and/or a predefined resolution.

In some embodiments, the device 100 displays the thumbnailrepresentation of the screenshot image at a location overlaid on the webbrowser interface 502 that satisfies an occlusion criterion. In oneexample, the selected location that satisfies the occlusion criterionoccludes the least number of pixels of the web browser interface 502. Inanother example, the selected location that satisfies the occlusioncriterion occludes the least number of pixels of the content displayedwithin the content region 504.

According to some embodiments, in response to detecting the screenshotcapture input, the device 100 displays the thumbnail representation ofthe screenshot image overlaid on the web browser interface 502.According to some embodiments, in response to detecting the screenshotcapture input, the device 100 displays the thumbnail representation ofthe screenshot image overlaid on the web browser interface 502 accordingto a predefined animation such as the fade-in animation in FIGS. 5B-5Dwhere the opacity of the thumbnail representation of the screenshotimage decreases and/or sharpness of the thumbnail representation of thescreenshot image increases. In some embodiments, in response todetecting the screenshot capture input, the device 100 also saves/storesthe screenshot image in an image storage repository (e.g., the cameraroll or image/media directory).

FIG. 5C illustrates displaying a thumbnail representation 514B of thescreenshot image 534 in a second state (e.g., a second opacity and/orsharpness level or a second fade-in state) overlaid on the web browserinterface 502. FIG. 5D illustrates displaying a thumbnail representation514C of the screenshot image 534 in a third state (e.g., a third opacityand/or sharpness level or a third fade-in state) overlaid on the webbrowser interface 502.

FIGS. 5D-5K show a sequence in which a screenshot image is edited (e.g.,modified and/or annotated) within a screenshot editing interface. FIG.5D also illustrates detecting a contact 516 (e.g., a tap/selectiongesture) at a location that corresponds to the thumbnail representation514C of the screenshot image 534. FIG. 5E illustrates replacing displayof the web browser interface 502 with a screenshot editing interface 520in response to the selection of the thumbnail representation 514C of thescreenshot image 534 in FIG. 5D.

As shown in FIG. 5E, the screenshot editing interface 520 includes thescreenshot image 534 within an image area bounded by cropping interfaceelements (e.g., crop handles) 532A, 532B, 532C, and 532D (sometimescollectively referred to herein as the “cropping interface elements532”).

As shown in FIG. 5E, the screenshot editing interface 520 includesaffordances 522A, 522B, 524, 526, 528, and 530. According to someembodiments, in response to activation (e.g., selection with a contact)of the affordance 522A (e.g., the undo affordance), the device 100reverts one or more previous modifications to the screenshot image 534.According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 522B (e.g., the redoaffordance), the device 100 reapplies one or more previously revertedmodifications to the screenshot image 534. According to someembodiments, in response to activation (e.g., selection with a contact)of the affordance 524 (e.g., the done affordance), the device 100replaces display of the screenshot editing interface 520 with the webbrowser interface 502 in FIG. 5A. In some embodiments, the device 100also saves/stores the modified screenshot image in addition to theunmodified screenshot image in an image storage repository (e.g., thecamera roll or image/media content library) in response to the selectionof the affordance 524. In some embodiments, the device 100 periodicallysaves/stores intermediate versions of the modified screenshot image inthe image storage repository prior to detecting selection of theaffordance 524.

According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 526 (e.g., the shareaffordance), the device 100 displays a transport interface overlaid onthe screenshot editing interface 520 provided to share the screenshotimage 534 via one or more communication means, such as email, SMS, etc.,and/or to perform one of a plurality of operations on the web page suchas a copy operation, a print operation, etc. (e.g., similar to thetransport interface 570 in FIG. 5L and the transport interface 650 inFIG. 6B). According to some embodiments, in response to activation(e.g., selection with a contact) of the affordance 528 (e.g., the markupaffordance), the device 100 displays a plurality of markup tools and acolor/appearance palate within the screenshot editing interface 520(e.g., as shown in FIGS. 5F-5G).

According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 530 (e.g., the deletionaffordance), the device 100 causes the modified screenshot image to bedeleted from the image storage repository. In some embodiments, thedevice 100 also deletes the unmodified screenshot image from the imagestorage repository in response to the selection of the affordance 530.In some embodiments, the device 100 replaces display of the screenshotediting interface 520 with the web browser interface 502 in FIG. 5A inresponse to the selection of the affordance 530.

FIG. 5E also illustrates detecting a first annotation input with acontact 536 according to motion path 538 (e.g., a circular tap-and-dragmotion) in order to circle the word “Caesar” within the screenshot image534. FIG. 5F illustrates displaying a first annotation 540 (e.g.,circling the word “Caesar”) over the screenshot image 534 in response todetecting the first annotation input in FIG. 5E.

FIG. 5F also illustrates detecting a contact 542 (e.g., a tap/selectiongesture) at a location that corresponds to the affordance 528. FIG. 5Gillustrates replacing display of the affordance 528 with a plurality ofmarkup tools and a color/appearance palate in response to the selectionof the affordance 528 in FIG. 5F. As shown in FIG. 5G, the plurality ofmarkup tool includes a highlighter/underline tool affordance 544A, apen/marker tool affordance 544B, a pencil tool affordance 544C, a rulertool affordance 544D, and an eraser tool affordance 544E (sometimescollectively referred to herein as the “markup tool affordances 544”).According to some embodiments, selection of one of the markup toolaffordances 544 causes a subsequent annotation to be displayed over thescreenshot image 534 based on the selected one of the markup toolaffordances 544 (e.g., as shown in FIGS. 5G-5I).

As shown in FIG. 5G, the color/appearance palate 546 includes a firstset of user-selectable colors and/or appearance patterns for annotatingthe screenshot image 534. As shown in FIG. 5G, the palate indicators 548indicates that the color/appearance palate 546 includes additional setsof user-selectable colors and/or appearance patterns in addition to thefirst set of user-selectable colors and/or appearance patterns. Forexample, the additional sets of user-selectable colors and/or appearancepatterns are accessed by swiping left-to-right or right-to-left over thefirst set of user-selectable colors and/or appearance patterns. Inanother example, the additional sets of user-selectable colors and/orappearance patterns are accessed by selecting one of the palateindicators 548.

FIG. 5G also illustrates detecting a contact 550 (e.g., a tap/selectiongesture) at a location that corresponds to the highlighter/underlinetool affordance 544A. FIG. 5H illustrates detecting a second annotationinput with a contact 552 according to motion vector 554 (e.g., asubstantially horizontal tap-and-drag motion) in order to highlightand/or underline the word “Germans” within the screenshot image 534.FIG. 5I illustrates displaying a second annotation 556 (e.g.,highlighting and/or underlining the word “Germans”) over the screenshotimage 534 in response to detecting the second annotation input in FIG.5H.

FIG. 5I also illustrates detecting a first cropping input in a downwarddirection from a top edge of the screenshot image 534 with a contact 560(e.g., a tap-and-drag gesture). As shown in FIG. 5I, a first dimension(e.g., height) of the screenshot image 534 has a first value 558A. FIG.5J illustrates displaying a cropped-out portion 565A of the screenshotimage 534 in response to detecting the first cropping input in FIG. 5I.For example, the cropped-out portion 565A has an opacity value and/or ablur value that is greater than the screenshot image 534. As shown inFIG. 5J, the first dimension (e.g., height) of the screenshot image 534has a second value 558B that is less than the first value 558A in FIG.5I. According to some embodiments, the device 100 adjusts thecropped-out portion 565A based on the locations of the chrome region(e.g., the display region that includes the indicator(s) 402, the time404, and the battery status indicator 406), the address bar 506, and thecontent region 504.

FIG. 5J also illustrates detecting a second cropping input in an upwarddirection from a bottom edge of the screenshot image 534 with a contact564 (e.g., a tap-and-drag gesture). FIG. 5K illustrates displaying acropped-out portion 565B of the screenshot image 534 in response todetecting the second cropping input in FIG. 5J. For example, thecropped-out portion 565B has an opacity value and/or a blur value thatis greater than the screenshot image 534. As shown in FIG. 5K, the firstdimension (e.g., height) of the screenshot image 534 has a third value558C that is less than the first value 558A in FIG. 5I and the secondvalue 558B in FIG. 5J. According to some embodiments, the device 100adjusts the cropped-out portion 565B based on the locations of thetoolbar region and the content region 504.

FIGS. 5K-5M show a sequence in which the edited screenshot image isshared via an email. FIG. 5K also illustrates detecting a contact 568(e.g., a tap/selection gesture) at a location corresponding to theaffordance 526 (e.g., the share affordance). FIG. 5L illustratesdisplaying a transport interface 570 over the screenshot editinginterface 520 in response to detecting selection of the affordance 526in FIG. 5K. As shown in FIG. 5L, the transport interface 570 includes alocal sharing affordance 572 provided to share the screenshot image 534(e.g., as modified in FIGS. 5E-5K) via a local interface (e.g.,BLUETOOTH, NFC, WiFi, and/or the like), sharing affordances 574A, 574B,574C, and 574D (sometimes collectively referred to herein as the“sharing affordances 574”) provided to share the screenshot image 534(e.g., as modified in FIGS. 5E-5K) via corresponding communication means(e.g., SMS, email, cloud storage, and others), and operation affordances576A, 576B, 576C, and 576D (sometimes collectively referred to herein asthe “operation affordances 576”) provided to perform correspondingoperations on the screenshot image 534 (e.g., as modified in FIGS.5E-5K).

FIG. 5L also illustrates detecting a contact 578 (e.g., a tap/selectiongesture) at a location corresponding to the sharing affordance 574B(e.g., the email sharing affordance). FIG. 5M illustrates replacingdisplay of the screenshot editing interface 520 with an emailcomposition interface 580 in response to the selection of the sharingaffordance 574B in FIG. 5L. As shown in FIG. 5M, the email compositioninterface 580 includes an email content/body region 586 with thescreenshot image 534 (e.g., as modified in FIGS. 5E-5K) and a link 588(e.g., a URI or URL) to the web page displayed in the web browser 502 inFIG. 5A.

FIGS. 5N-5O show a sequence in which the thumbnail representation of thescreenshot image ceases to be displayed over the web browser interface.The web browser interface 502 in FIG. 5N is similar to and adapted fromthe web browser interface 502 in FIG. 5D. As such, FIG. 5D and FIG. 5Ninclude similar user interfaces and elements labeled with the samereference number in both figures have the same function, with only thedifferences described herein for the sake of brevity. FIG. 5Nillustrates detecting a right-to-left swipe gesture over the thumbnailrepresentation 514C of the screenshot image 534 with a contact 580(e.g., a tap-and-drag gesture). FIG. 5O illustrates ceasing to displaythe thumbnail representation 514C of the screenshot image 534 over webbrowser interface 502 in response to detecting the right-to-left swipegesture over the thumbnail representation 514C of the screenshot image534 in FIG. 5N.

FIG. 5P illustrates displaying a web browser interface 5100 associatedwith a web browser application executed by the device 100. As shown inFIG. 5P, the web browser interface 5100 includes a toolbar region 5103,a tab bar region 5105, and a content region 5107. In FIG. 5P, thetoolbar region 5103 includes a back affordance 5115 a provided todisplay a previous web page in response to selection thereof (e.g., witha contact), a next affordance 5115 b provided to display a next web pagein response to selection thereof, and a book mark affordance 5115 cprovided to replace display of the web browser interface 5100 with abookmark management interface in response to selection thereof.

In FIG. 5P, the toolbar region 5103 also includes an address bar 5104displaying URL 5108 for tab 5106-A and a refresh affordance 5119provided to refresh/reload the current web page in response to selectionthereof (e.g., with a contact). In FIG. 5P, the toolbar region 5103further includes a sharing affordance 5109 provided to display atransport interface over the web browser interface 5100 in response toselection thereof (e.g., similar to the transport interface 570 in FIG.5L and the transport interface 650 in FIG. 6B), an add tab affordance5111 provided to add a tab to the web browser interface 5100 in responseto selection thereof (e.g., with a contact), and a tab view affordance5113 provided to replace display of the web browser interface 5100 witha tab management interface in response to selection thereof.

In FIG. 5P, the tab bar region 5105 includes a plurality ofuser-selectable tabs 5106-A, 5106-B, and 5106-C (sometimes collectivelyreferred to herein as the “tabs 5106”) provided to display associatedcontent within the content region 5107 in response to selection thereof.As shown in FIG. 5P, the tab 5106-A is currently selected, and thecontent region 5107 includes content 5110 for the tab 5106-A.

FIGS. 5P-5U show a sequence in which a group of thumbnailrepresentations of screenshot images are overlaid on the web browserinterface. For example, the device 100 detects a first screenshotcapture input such as a predefined gesture, voice command, keycombination (e.g., print screen key, power+home button combination,etc.), and/or the like. FIG. 5Q illustrates displaying a first thumbnailrepresentation 5120 of a first screenshot image 5136 (e.g., the webbrowser interface 5100 displaying the content 5110 for the tab 5106-A)over the web browser interface 5100 in response to detecting the firstscreenshot capture input.

FIG. 5Q also illustrates detecting a contact 5122 (e.g., a tap/selectiongesture) at a location corresponding to the tab 5106-B. FIG. 5Rillustrates updating the web browser interface 5100 to shown the content5112 for the tab 5106-B within the content region 5107 and the URL 5116for the tab 5106-B within the address bar 5104 in response to theselection of the tab 5106-B in FIG. 5Q. For example, the tab 5106-B iscurrently selected in FIG. 5R in response to the selection of the tab5106-B in FIG. 5Q. For example, the device 100 detects a secondscreenshot capture input such as a predefined gesture, voice command,key combination (e.g., print screen key, power+home button combination,etc.), and/or the like. FIG. 5S illustrates displaying a secondthumbnail representation 5124 of a second screenshot image 5134 (e.g.,the web browser interface 5100 displaying the content 5112 for the tab5106-B) in addition to the first thumbnail representation 5120 of thefirst screenshot image 5136 over the web browser interface 5100 inresponse to detecting the second screenshot capture input.

FIG. 5S also illustrates detecting a contact 5126 (e.g., a tap/selectiongesture) at a location corresponding to the tab 5106-C. FIG. 5Tillustrates updating the web browser interface 5100 to shown the content5114 for the tab 5106-C within the content region 5107 and the URL 5118for the tab 5106-C within the address bar 5104 in response to theselection of the tab 5106-C in FIG. 5S. For example, the tab 5106-C iscurrently selected in FIG. 5T in response to the selection of the tab5106-C in FIG. 5S. For example, the device 100 detects a thirdscreenshot capture input such as a predefined gesture, voice command,key combination (e.g., print screen key, power+home button combination,etc.), and/or the like. FIG. 5U illustrates displaying a third thumbnailrepresentation 5128 of a third screenshot image 5132 (e.g., the webbrowser interface 5100 displaying the content 5114 for the tab 5106-A)in addition to the first thumbnail representation 5120 of the firstscreenshot image 5136 and the second thumbnail representation 5124 ofthe second screenshot image 5134 over the web browser interface 5100 inresponse to detecting the third screenshot capture input.

FIGS. 5U-5X show a sequence in which one of the screenshot images isedited (e.g., modified and/or annotated) within the screenshot editinginterface. FIG. 5U also illustrates detecting a contact 5130 (e.g., atap/selection gesture) at a location that corresponds to the group ofthumbnail representations 5120, 5124, and 5128. FIG. 5V illustratesreplacing display of the web browser interface 5100 with a screenshotediting interface 520 in response to the selection of the group ofthumbnail representations 5120, 5124, and 5128 in FIG. 5U.

The screenshot editing interface 520 in FIG. 5V is similar to andadapted from the screenshot editing interface 520 in FIG. 5E. As such,FIG. 5E and FIG. 5V include similar user interfaces and elements labeledwith the same reference number in both figures have the same function,with only the differences described herein for the sake of brevity. Asshown in FIG. 5V, the screenshot editing interface 520 includes thethird screenshot image 5132 (e.g., associated with the third thumbnailrepresentation 5128 in FIG. 5U) within an image area bounded by croppinginterface elements 532 (e.g., crop handles). As shown in FIG. 5V, thescreenshot editing interface 520 includes a portion of the secondscreenshot image 5134 (e.g., associated with the second thumbnailrepresentation 5124 in FIGS. 5S-5T). According to some embodiments, theuser is able to individually modify the third screenshot image 5132, thesecond screenshot image 5134, and the first screenshot image 5136 withinthe screenshot editing interface 520. According to some embodiments, theuser is able to navigate between the third screenshot image 5132, thesecond screenshot image 5134, and the first screenshot image 5136 withinthe screenshot editing interface 520 (e.g., with a swipe gesture asshown in FIGS. 5V-5W).

FIG. 5V also illustrates detecting a navigation gesture with a contact5138 (e.g., a right-to-left swipe or tap-and-drag gesture) within thescreenshot editing interface 520. FIG. 5W illustrates updating thescreenshot editing interface 520 to show the second screenshot image5134 (e.g., associated with the second thumbnail representation 5124 inFIGS. 5S-5T) within an image area bounded by cropping interface elements532 (e.g., crop handles). As shown in FIG. 5W, the screenshot editinginterface 520 also includes a portion of the third screenshot image 5132(e.g., associated with the third thumbnail representation 5128 in FIG.5U) and a portion of the first screenshot image 5136 (e.g., associatedwith the first thumbnail representation 5120 in FIGS. 5Q-5R).

FIG. 5W also illustrates detecting a cropping input in a downwarddirection from a top edge of the second screenshot image 5134 with acontact 5140 (e.g., a tap-and-drag gesture). FIG. 5X illustratesdisplaying a cropped-out portion 5135 of the second screenshot image5134 in response to detecting the cropping input in FIG. 5W. Forexample, the cropped-out portion 5135 has an opacity value and/or a blurvalue that is greater than the second screenshot image 5134. Accordingto some embodiments, the device 100 adjusts the cropped-out portion 5135based on paragraph breaks and/or carriage returns within the content5112.

FIG. 5Y illustrates displaying a split-screen user interface thatincludes a first region associated with a web browser interface 5100 anda second region associated with a messaging interface 5150. For example,the web browser interface 5100 is associated with a web browserapplication executed by the device 100. For example, the messaginginterface 5150 is associated with a messaging application (e.g., instantmessaging, text messaging, etc.) executed by the device 100. As shown inFIG. 5Y, the first and second regions are separated by a divider element5149. According to some embodiments, the device 100 updates at least onedimension (e.g., width) of the first and second regions in response todetecting a user input that interacts with the divider element 5149(e.g., a tap-and-drag gesture in a left-to-right or right-to-leftdirection).

The web browser interface 5100 in FIG. 5Y is similar to and adapted fromthe web browser interface 5100 in FIG. 5T. As such, FIG. 5T and FIG. 5Yinclude similar user interfaces and elements labeled with the samereference number in both figures have the same function, with only thedifferences described herein for the sake of brevity. The messaginginterface 5150 includes a message input field 5152 provided to receiveone or more input characters (e.g., via a software keyboard orspeech-to-text application), images, emoticons, and/or the like for anew message within the current messaging thread.

FIGS. 5Y-5Z show a sequence in which a thumbnail representation of ascreenshot image is overlaid on a split-screen user interface. Forexample, the device 100 detects a screenshot capture input such as apredefined gesture, voice command, key combination (e.g., print screenkey, power+home button combination, etc.), and/or the like. FIG. 5Zillustrates displaying a thumbnail representation 5158 of a screenshotimage 5168 (e.g., the web browser interface 5100 displaying the content5114 for the tab 5106-C) over the web browser interface 5100 in responseto detecting the screenshot capture input.

FIGS. 5Z-5AA show a sequence in which the thumbnail representation ofthe screenshot image is dragged-and-dropped into one of the regions ofthe split-screen user interface. FIG. 5Z also illustrates detecting adrag-and-drop gesture with a contact 5160 that drags the thumbnailrepresentation 5158 of the screenshot image 5168 into the second regionassociated with the messaging interface 5150 and drops the thumbnailrepresentation 5158 of the screenshot image 5168 into the message inputfield 5152. FIG. 5AA illustrates displaying the thumbnail representation5158 of the screenshot image 5168 within the message input field 5152 inresponse to detecting the drag-and-drop gesture in FIG. 5Z. As shown inFIG. 5AA, the message input field 5152 includes a comment field 5162 foradding a comment to the new message and a send affordance 5164 providedto send the new message in response to selection thereof.

FIGS. 5AA-5CC show a sequence in which the screenshot image is edited(e.g., modified and/or annotated) within the screenshot editinginterface. FIG. 5AA also illustrates detecting a contact 5166 (e.g., atap/selection gesture) at a location that corresponds to the thumbnailrepresentation 5158 of the screenshot image 5168 within the first regionassociated with the web browser interface 5100. FIG. 5BB illustratesreplacing display of the split-screen user interface with a screenshotediting interface 520 in response to the selection of the thumbnailrepresentation 5158 of the screenshot image 5168 within the first regionin FIG. 5AA.

The screenshot editing interface 520 in FIG. 5BB is similar to andadapted from the screenshot editing interface 520 in FIG. 5E. As such,FIG. 5E and FIG. 5BB include similar user interfaces and elementslabeled with the same reference number in both figures have the samefunction, with only the differences described herein for the sake ofbrevity. As shown in FIG. 5BB, the screenshot editing interface 520includes the screenshot image 5168 within an image area bounded bycropping interface elements 532 (e.g., crop handles).

FIG. 5BB also illustrates detecting a cropping input in a right-to-leftdirection from a right edge of the screenshot image 5168 with a contact5170 (e.g., a tap-and-drag gesture). As shown in FIG. 5BB, a firstdimension (e.g., width) of the screenshot image 5168 has a first value5172A. FIG. 5CC illustrates displaying a cropped version of thescreenshot image 5168 in response to detecting the cropping input inFIG. 5BB. As shown in FIG. 5CC, the first dimension (e.g., width) of thescreenshot image 5168 has a second value 5172B that is less than thefirst value 5172A in FIG. 5BB. According to some embodiments, the device100 adjusts the cropped version of the screenshot image 5168 based onthe divider element 5149 and the first and second regions of thesplit-screen user interface.

FIGS. 6A-6N illustrate example user interfaces for expanding ascreenshot image within a screenshot editing interface in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the process in FIGS.8A-8C. Although some of the examples which follow will be given withreference to inputs on a touch-screen display (where the touch-sensitivesurface and the display are combined), in some embodiments, the devicedetects inputs on a touch-sensitive surface 451 that is separate fromthe display 450, as shown in FIG. 4B.

FIG. 6A illustrates displaying a web browser interface 600 associatedwith a web browser application executed by the device 100. As shown inFIG. 6A, the web browser interface 600 includes a toolbar region 603, atab bar region 605, and a content region 607. In FIG. 6A, the toolbarregion 603 includes a back affordance 615 a provided to display aprevious web page in response to selection thereof (e.g., with acontact), a next affordance 615 b provided to display a next web page inresponse to selection thereof, and a book mark affordance 615 c providedto replace display of the web browser interface 600 with a bookmarkmanagement interface in response to selection thereof.

In FIG. 6A, the toolbar region 603 also includes an address bar 604displaying URL 608 for tab 606-A and a refresh affordance 619 providedto refresh/reload the current web page in response to selection thereof(e.g., with a contact). In FIG. 6A, the toolbar region 603 furtherincludes a sharing affordance 609 provided to display a transportinterface over the web browser interface 600 in response to selectionthereof (e.g., as shown in FIGS. 6A-6B), an add tab affordance 611provided to add a tab to the web browser interface 600 in response toselection thereof (e.g., with a contact), and a tab view affordance 613provided to replace display of the web browser interface 600 with a tabmanagement interface in response to selection thereof. In FIG. 6A, thetab bar region 605 includes a user-selectable tab 606-A, and the contentregion 607 includes content 610 for the tab 606-A.

FIGS. 6A-6C show a sequence in which a thumbnail representation of ascreenshot image is overlaid on the web browser interface. FIG. 6Aillustrates detecting a contact 625 (e.g., a tap/selection gesture) at alocation corresponding to the sharing affordance 609 (e.g., the shareaffordance). FIG. 6B illustrates displaying a transport interface 650over the web browser interface 600 in response to the selection of thesharing affordance 609 in FIG. 6A.

As shown in FIG. 6B, the transport interface 650 includes a localsharing affordance 652 provided to share the web page via a localinterface (e.g., BLUETOOTH, NFC, WiFi, and/or the like), sharingaffordances 654A, 654B, 654C, and 654D (sometimes collectively referredto herein as the “sharing affordances 654”) provided to share the webpage via corresponding communication means (e.g., SMS, email, cloudstorage, and others), and operation affordances 656E, 656A, 656B, and656D (sometimes collectively referred to herein as the “operationaffordances 656”) provided to perform corresponding operations on theweb page (e.g., screenshot capture, save, copy, print, etc.).

FIG. 6B also illustrates detecting a contact 637 (e.g., a tap/selectiongesture) at a location corresponding to the operation affordance 656E(e.g., the screenshot capture operation). FIG. 6C illustrates displayinga thumbnail representation 627 of a screenshot image 640 over the webbrowser interface 600 in response to the selection of the operationaffordance 656E in FIG. 6B. For example, the screenshot image 640 isshrunk to generate the thumbnail representation 627 based on predefineddimensions, a predefined aspect ratio, and/or a predefined resolution.

FIGS. 6C-6E show a sequence in which the screenshot image is expandedwithin the screenshot editing interface. FIG. 6C also illustratesdetecting a contact 629 (e.g., a tap/selection gesture) at a locationthat corresponds to the thumbnail representation 627 of the screenshotimage 640. FIG. 6D illustrates replacing display of the web browserinterface 600 with a screenshot editing interface 620 in response to theselection of the thumbnail representation 627 of the screenshot image640 in FIG. 6C.

As shown in FIG. 6D, the screenshot editing interface 620 includes thescreenshot image 640 within an image area bounded by cropping interfaceelements (e.g., crop handles) 632A, 632B, 632C, and 632D (sometimescollectively referred to herein as the “cropping interface elements632”). In FIG. 6D, a first portion 642 of the content associated withthe URL 608 (e.g., content that was displayed within the web browserinterface 600 in FIG. 6A) is displayed within the image area bounded bythe cropping interface elements 632. Additionally, in FIG. 6D, a secondportion 644 of the content associated with the URL 608 (e.g., contentthat was not displayed within the web browser interface 600 in FIG. 6A)is displayed outside of the image area bounded by the cropping interfaceelements 632.

According to some embodiments, the second portion 644 of the contentassociated with the URL 608 is pre-fetched by the web browserapplication. According to some embodiments, the second portion 644 ofthe content associated with the URL 608 is optionally displayed withinthe screenshot editing interface 620 in FIG. 6D to indicate that theuser has the option to expand the screenshot image to include contentthat was not displayed within the web browser interface 600 in FIG. 6A.

As shown in FIG. 6D, the screenshot editing interface 620 includesaffordances 622A, 622B, 624, 626, 628, and 630. According to someembodiments, in response to activation (e.g., selection with a contact)of the affordance 622A (e.g., the undo affordance), the device 100reverts one or more previous modifications to the screenshot image 640.According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 622B (e.g., the redoaffordance), the device 100 reapplies one or more previously revertedmodifications to the screenshot image 640. According to someembodiments, in response to activation (e.g., selection with a contact)of the affordance 624 (e.g., the done affordance), the device 100replaces display of the screenshot editing interface 620 with the webbrowser interface 600 in FIG. 6C. In some embodiments, the device 100also saves/stores the modified screenshot image in addition to theunmodified screenshot image in an image storage repository (e.g., thecamera roll or image/media content library) in response to the selectionof the affordance 624. In some embodiments, the device 100 periodicallysaves/stores intermediate versions of the modified screenshot image inthe image storage repository prior to detecting selection of theaffordance 624.

According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 626 (e.g., the shareaffordance), the device 100 displays a transport interface overlaid onthe screenshot editing interface 620 provided to share the screenshotimage 640 via one or more communication means, such as email, SMS, etc.,and/or to perform one of a plurality of operations on the web page suchas a copy operation, a print operation, etc. (e.g., as shown in FIGS.6E-6F and FIGS. 6L-6M). According to some embodiments, in response toactivation (e.g., selection with a contact) of the affordance 628 (e.g.,the markup affordance), the device 100 displays a plurality of markuptools and a color/appearance palate within the screenshot editinginterface 620 (e.g., as shown in FIGS. 5F-5G).

According to some embodiments, in response to activation (e.g.,selection with a contact) of the affordance 630 (e.g., the deletionaffordance), the device 100 causes the modified screenshot image to bedeleted from the image storage repository. In some embodiments, thedevice 100 also deletes the unmodified screenshot image from the imagestorage repository in response to the selection of the affordance 630.In some embodiments, the device 100 replaces display of the screenshotediting interface 620 with the web browser interface 600 in FIG. 6A inresponse to the selection of the affordance 630.

FIG. 6D also illustrates detecting an expansion input in a downwarddirection from a bottom edge of the screenshot image 640 with a contact636 (e.g., a tap-and-drag gesture). As shown in FIG. 6D, the screenshotimage 640 includes the first portion 642 of the content associated withthe URL 608 displayed within the image area bounded by croppinginterface elements 632.

FIG. 6E illustrates displaying the first portion 642 and the secondportion 644 within the image area bounded by cropping interface elements632 in response to detecting the expansion input in FIG. 6D. As such, inFIG. 6E, the screenshot image 640 includes the first portion 642 of thecontent associated with the URL 608 and the second portion 644 of thecontent associated with the URL 608. As shown in FIG. 6E, the dimensionsof the screenshot image 640 are maintained between FIGS. 6D and 6E. Assuch, the device appends the second portion 644 of the contentassociated with the URL 608 to the first portion 642 of the contentassociated with the URL 608 and scrolls the screenshot image. As shownin FIG. 6E, the screenshot editing interface 620 includes a “scroll tosee more” indicator 648 to alert the user that a portion of thescreenshot image has been scrolled and may be viewed in response todetecting a scroll input within the screenshot interface 620 (e.g., avoice command, or an upward or downward swipe gesture over thescreenshot image 640).

Additionally, in FIG. 6E, a third portion 646 of the content associatedwith the URL 608 (e.g., content that was not displayed within the webbrowser interface 600 in FIG. 6A) is displayed outside of the image areabounded by the cropping interface elements 632. According to someembodiments, the third portion 646 of the content associated with theURL 608 is pre-fetched by the web browser application. According to someembodiments, the third portion 646 of the content associated with theURL 608 is optionally displayed within the screenshot editing interface620 in FIG. 6E to indicate that the user has the option to furtherexpand the screenshot image to include content that was not displayedwithin the web browser interface 600 in FIG. 6A.

FIGS. 6E-6G show a sequence in which the expanded screenshot image isshared via a message. FIG. 6E also illustrates detecting a contact 638(e.g., a tap/selection gesture) at a location corresponding to theaffordance 626 (e.g., the share affordance). FIG. 6F illustratesdisplaying the transport interface 650 over the screenshot editinginterface 620 in response to detecting selection of the affordance 626in FIG. 6E. The web transport interface 650 in FIG. 6F is similar to andadapted from the transport interface 650 in FIG. 6B. As such, FIG. 6Band FIG. 6F include similar user interfaces and elements labeled withthe same reference number in both figures have the same function, withonly the differences described herein for the sake of brevity.

FIG. 6F also illustrates detecting a contact 658 (e.g., a tap/selectiongesture) at a location corresponding to the sharing affordance 654A(e.g., the SMS sharing affordance). FIG. 6G illustrates replacingdisplay of the screenshot editing interface 620 with a messagecomposition interface 660 in response to the selection of the sharingaffordance 654A in FIG. 6F. As shown in FIG. 6G, the message compositioninterface 660 includes the screenshot image 640 (e.g., as expanded inFIGS. 6D-6E), a comment field 662 for adding a comment to the newmessage via the software (SW) keyboard 666 (or other input means), and asend affordance 664 provided to send the new message in response toselection thereof.

FIG. 6H illustrates displaying a messaging interface 6100 associatedwith a messaging application (e.g., instant messaging, text messaging,etc.) executed by the device 100. As shown in FIG. 6H, the messaginginterface 6100 includes a plurality of messages 6102A, 6102B, 6102C,6102D, 6102E, 6102F, 6102G, and 6102H (sometimes collectively referredto herein as the “messages 6102”). As shown in FIG. 6H, the messaginginterface 6100 also includes a message input field 6104 provided toreceive one or more input characters (e.g., via a software keyboard orspeech-to-text application), images, emoticons, and/or the like for anew message within the current messaging thread.

FIGS. 6H-6I show a sequence in which a thumbnail representation of ascreenshot image is overlaid on the messaging interface. For example,the device 100 detects a screenshot capture input such as a predefinedgesture, voice command, key combination (e.g., print screen key,power+home button combination, etc.), and/or the like. FIG. 6Iillustrates displaying a thumbnail representation 6106 of a screenshotimage 6110 overlaid on the messaging interface 6100 in response todetecting the screenshot capture input. For example, the screenshotimage 6110 corresponds to the messaging interface 6100 displayed in FIG.6H. For example, the screenshot image 6110 is shrunk to generate thethumbnail representation 6106 based on predefined dimensions, apredefined aspect ratio, and/or a predefined resolution.

FIGS. 6I-6L show a sequence in which the screenshot image is expandedwithin the screenshot editing interface. FIG. 6I also illustratesdetecting a contact 6108 (e.g., a tap/selection gesture) at a locationthat corresponds to the thumbnail representation 6106 of the screenshotimage 6110. FIG. 6J illustrates replacing display of the messaginginterface 6100 with a screenshot editing interface 620 in response tothe selection of the thumbnail representation 6106 of the screenshotimage 6110 in FIG. 6I.

The screenshot editing interface 620 in FIG. 6J is similar to andadapted from the screenshot editing interface 620 in FIG. 6D. As such,FIG. 6D and FIG. 6J include similar user interfaces and elements labeledwith the same reference number in both figures have the same function,with only the differences described herein for the sake of brevity.

As shown in FIG. 6J, the screenshot editing interface 620 includes thescreenshot image 6110 within an image area bounded by cropping interfaceelements 632 (e.g., crop handles). In FIG. 6J, a first portion 6112 ofthe messaging content associated with messages 6102A, 6102B, 6102C,6102D, 6102E, 6102F, 6102G, and 6102H (e.g., content that was displayedwithin the messaging interface 610 in FIG. 6H) is displayed within theimage area bounded by the cropping interface elements 632. Additionally,in FIG. 6J, a second portion 6114 of the messaging content associatedwith messages 6102I, 6102J, and 6102K (e.g., content that was notdisplayed within the messaging interface 610 in FIG. 6H) is displayedoutside of the image area bounded by the cropping interface elements632.

According to some embodiments, the second portion 6114 of the messagingcontent associated with messages 6102I, 6102J, and 6102K is pre-fetchedby the messaging application. According to some embodiments, the secondportion 6114 of the messaging content associated with messages 6102I,6102J, and 6102K is optionally displayed within the screenshot editinginterface 620 in FIG. 6J to indicate that the user has the option toexpand the screenshot image to include messaging content that was notdisplayed within the messaging interface 6100 in FIG. 6H.

FIG. 6J also illustrates detecting an expansion input in an upwarddirection from a top edge of the screenshot image 6110 with a contact6122 (e.g., a tap-and-drag gesture). As shown in FIG. 6J, the screenshotimage 6110 includes the first portion 6112 of the messaging contentassociated with messages 6102A, 6102B, 6102C, 6102D, 6102E, 6102F,6102G, and 6102H displayed within the image area bounded by croppinginterface elements 632.

FIG. 6K illustrates displaying the first portion 6112 and the secondportion 6114 within the image area bounded by cropping interfaceelements 632 in response to detecting the extent of the dragging portionof the expansion input in FIG. 6J (but not lift-off of the contact6122). FIG. 6L illustrates displaying a third portion 6116 of themessaging content associated with messages 6102L, 6102M, 6102N, and6102O (e.g., content that was not displayed within the messaginginterface 610 in FIG. 6H) outside of the image area bounded by thecropping interface elements 632 in response to detecting lift-off of theexpansion input in FIGS. 6J-6K. As such, in FIG. 6L, the screenshotimage 6110 includes the first portion 6112 of the messaging contentassociated with messages 6102A, 6102B, 6102C, 6102D, 6102E, 6102F,6102G, and 6102H and the second portion 6114 of the messaging contentassociated with messages 6102I, 6102J, and 6102K. As shown in FIG. 6L,the device 100 shrinks the dimensions of the screenshot image 6110between FIGS. 6J-6L to display the entirety of the expanded screenshotimage.

According to some embodiments, the third portion 6116 of the messagingcontent associated with messages 6102L, 6102M, 6102N, and 6102O ispre-fetched by the messaging application. According to some embodiments,the third portion 6116 of the messaging content associated with messages6102L, 6102M, 6102N, and 6102O is optionally displayed within thescreenshot editing interface 620 in FIG. 6L to indicate that the userhas the option to further expand the screenshot image to include contentthat was not displayed within the messaging interface 6100 in FIG. 6H.

FIGS. 6L-6N show a sequence in which the expanded screenshot image isshared via an email. FIG. 6L also illustrates detecting a contact 6124(e.g., a tap/selection gesture) at a location corresponding to theaffordance 626 (e.g., the share affordance). FIG. 6M illustratesdisplaying the transport interface 650 over the screenshot editinginterface 620 in response to detecting selection of the affordance 626in FIG. 6L. The web transport interface 650 in FIG. 6M is similar to andadapted from the transport interface 650 in FIGS. 6B and 6F. As such,FIG. 6B, FIG. 6F, and FIG. 6M include similar user interfaces andelements labeled with the same reference number in both figures have thesame function, with only the differences described herein for the sakeof brevity.

FIG. 6M also illustrates detecting a contact 6126 (e.g., a tap/selectiongesture) at a location corresponding to the sharing affordance 654B(e.g., the email sharing affordance). FIG. 6N illustrates replacingdisplay of the screenshot editing interface 620 with an emailcomposition interface 6150 in response to the selection of the sharingaffordance 654B in FIG. 6M. As shown in FIG. 6N, the email compositioninterface 6150 includes an email content/body region 6156 with thescreenshot image 6110 (e.g., as expanded in FIGS. 6J-6L) and anapplication store or download link 6158 (e.g., a URI or URL) to themessaging application associated with the messaging interface 6100 inFIG. 6H.

FIGS. 7A-7E illustrate a flow diagram of a method 700 of editing ascreenshot image in accordance with some embodiments. The method 700 isperformed at an electronic device (e.g., the portable multifunctiondevice 100 in FIG. 1A, or the device 300 in FIG. 3) with one or moreprocessors, non-transitory memory, a display, and one or more inputdevices. In some embodiments, the display is a touch-screen display andthe one or more input devices are on or integrated with the display(e.g., the device is a tablet or smartphone). In some embodiments, thedisplay is separate from the one or more input devices (e.g., the deviceis a laptop with a separate display and touchpad, or desktop computerwith a separate display and mouse). Some operations in method 700 are,optionally, combined and/or the order of some operations is, optionally,changed.

As described below, the method 700 provides an intuitive way to edit ascreenshot image. The method reduces the cognitive burden on a user whenediting a screenshot image, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to edit a screenshot image faster and more efficientlyconserves power and increases the time between battery charges.

While displaying content on the display, the device detects (702), viathe one or more input devices, a screenshot capture input. According tosome embodiments, the “content” displayed on the display generallycorresponds to an application interface. For example, the contentcorresponds to a web page displayed within a web browser application, amessage thread within an email application or messaging application, allor a portion of a PDF file, all or a portion of an image file, all or aportion of a document file, or the like. In another example, the contentincludes objects/icons associated with media items displayed within amedia consumption/organization application, within a file explorerapplication, or within a device home screen. In some embodiments, thescreenshot capture input corresponds to a keypress (e.g., print screenkey) or a keypress combination (e.g., home button+power button). In someembodiments, the screenshot capture input corresponds to selection of anassociated affordance (e.g., through a sharing panel or transportinterface).

In response to detecting the screenshot capture input, the device (704):captures a screenshot image of the content displayed on the display; anddisplays, on the display, a thumbnail representation of the screenshotimage overlaid on the content displayed on the display and capturedwithin the screenshot image. In some embodiments, in response todetecting the screenshot capture input, the device saves/stores thescreenshot image in an image storage repository such as the camera rollor image/media content library. In some embodiments, the screenshotimage includes the entire display area of the device. In someembodiments, the screenshot image includes a portion of the display areaof the device (e.g., including application related content but excludingOS related content such as an OS chrome bar). In some embodiments, thethumbnail representation is displayed at a location that reducesocclusion of the underlying content. According to some embodiments, thethumbnail representation of the screenshot image provides a visual cueindicating that the screenshot capture input was successful and that thescreenshot image may be modified or interacted with.

As one example, in FIG. 5B, the device 100 displays a thumbnailrepresentation 514A of a screenshot image 534 in a first state (e.g., afirst opacity and/or sharpness level or a first fade-in state) overlaidon the web browser interface 502 in response to detecting the screenshotcapture input. For example, the screenshot image 534 corresponds to theweb browser interface 502 displayed in FIG. 5A. For example, thescreenshot image 534 is shrunk to generate the thumbnail representation514A based on predefined dimensions, a predefined aspect ratio, and/or apredefined resolution. As another example, in FIG. 5Q, the device 100displays a first thumbnail representation 5120 of a first screenshotimage 5136 (e.g., of the web browser interface 5100 with the tab 5106-Aopen) over the web browser interface 5100 in response to detecting thefirst screenshot capture input.

In some embodiments, in response to detecting the screenshot captureinput, the device places (706) the screenshot in an image storagerepository that is accessible via the device. In some embodiments, inresponse to detecting the screenshot capture input, the devicesaves/stores the screenshot image in an image storage repository such asthe camera roll or image/media content library. According to someembodiments, placing the screenshot image in the camera roll orimage/media content library provides a seamless user experience thatrequires less time and user inputs when saving/storing screenshotimages, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, displaying the thumbnail representation includes(708) displaying a predefined animation. For example, the predefinedanimation corresponds to a fade-in animation. In another example, thepredefined animation represents a simulation of film developing such asa gradual fade-in of the image from the edges toward the center or agradual fade-in of the image from the center toward the edges. FIGS.5B-5D show a sequence in which the thumbnail representation transitionsbetween states 514A, 514B, and 514C, respectively, where the opacitydecreases and the sharpness increases in order to illustrate a fade-inanimation. According to some embodiments, the predefined animationprovides a visual cue indicating that the screenshot capture input wassuccessful.

In some embodiments, the thumbnail representation of the screenshotimage is displayed (710) at a location overlaid on the content thatsatisfies an occlusion criterion. In some embodiments, the thumbnailrepresentation is overlaid at a location that reduces occlusion of thecontent. As such, the location of the thumbnail representation reducescluttering the display area and reduces intruding on the userexperience. According to some embodiments, displaying the thumbnailrepresentation of the screenshot image at a location that satisfies theocclusion criteria provides a seamless and non-intrusive user experiencewhen capturing screenshot images, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

As one example, in FIG. 5D, the thumbnail representation 514C isdisplayed at a location over the web browser interface 502 thatsatisfies the occlusion criterion (e.g., the bottom-left corner of theweb browser interface 502). In one example, the selected location of therepresentation 514C in FIG. 5D that satisfies the occlusion criterionoccludes the least number of pixels of the web browser interface 502. Inanother example, the selected location of the representation 514C inFIG. 5D that satisfies the occlusion criterion occludes the least numberof pixels of the content displayed within the content region 504.

The device detects (712), via the one or more input devices, arespective input directed to the thumbnail representation of thescreenshot image. In some embodiments, the respective input correspondsto a predetermined gesture, such as a tap, pinch, flick, or swipe, at alocation associated with the thumbnail representation. In someembodiments, the respective input corresponds to a mouse click at alocation associated with the thumbnail representation. In someembodiments, the respective input corresponds to a predefined keypresscombination. In some embodiments, the respective input corresponds to apredefined voice command. As one example, in FIG. 5D, the device 100detects a contact 516 (e.g., a tap/selection gesture) at a location thatcorresponds to the thumbnail representation 514C of the screenshot image534. As another example, in FIG. 5N, the device 100 detects a swiperight-to-left gesture over the thumbnail representation 514C of thescreenshot image with a contact 580 (e.g., a tap-and-drag gesture).

In response to detecting the respective input directed to the thumbnailrepresentation of the screenshot image, and in accordance with adetermination that the respective input corresponds to a selectioninput, the device displays (714), on the display, a screenshot editinginterface provided to edit the screenshot image, where the screenshotediting interface includes the screenshot image. In some embodiments,the application associated with the content ceases to be displayed onthe display. For example, the application associated with the contenttransitions to the background. In some embodiments, the content isreplaced with the screenshot editing interface display. In someembodiments, the screenshot editing interface is overlaid on thecontent. According to some embodiments, the screenshot editing interfaceprovides a seamless user experience that requires less time and userinputs when modifying screenshot images, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the selection input (e.g., the first type of input)corresponds to a tap or click on the thumbnail representation to enterthe screenshot editing interface. In some embodiments, a second type ofinput (e.g., a request to cease display of the thumbnail representation)corresponds to a right-to-left swipe gesture that causes the device toremove the thumbnail representation from the display and (optionally)delete the screenshot image from the camera roll. In some embodiments, athird type of selection input corresponds to a left-to-right swipegesture that causes the device to remove the thumbnail representationfrom the display and maintain storage of the screenshot image in thecamera roll.

As one example, FIGS. 5D-5E show a sequence in which the device replacesdisplay of the web browser interface 502 with the screenshot editinginterface 520 in response to detecting selection of the thumbnailrepresentation 514C with the contact 516 in FIG. 5D (e.g., with atap/selection input). As shown in FIG. 5E, the screenshot editinginterface 520 includes the screenshot image 534 associated with thethumbnail representation 514C. As another example, FIGS. 5U-5V show asequence in which the device replaces display of the web browserinterface 5100 with the screenshot editing interface 520 in response todetecting selection of the group of thumbnail representations 5120,5124, and 5128 with the contact 5130 in FIG. 5U (e.g., with atap/selection input). As shown in FIG. 5V, the screenshot editinginterface 520 includes the screenshot image 5132 associated with thethird thumbnail representation 5128.

In some embodiments, the screenshot editing interface includes (716) atleast one of a deletion affordance provided to delete the screenshotimage, a done affordance provided to save the screenshot image, asharing affordance provided to share the screenshot image, a markupaffordance provided to enable annotations to be applied to thescreenshot image, and one or more cropping interface elements (e.g.,crop handles that frame the corners of the screenshot image) provided tocrop the screenshot image. In some embodiments, the screenshot editinginterface also includes undo and redo affordances for rolling back orreapplying modifications to the screenshot image. According to someembodiments, the affordances within the screenshot editing interfaceprovides a seamless user experience that requires less time and userinputs when modifying screenshot images, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

As one example, in FIG. 5E, the screenshot editing interface 520includes an undo affordance 522A, a redo affordance 522B, a doneaffordance 524, a share affordance 526, a markup affordance 528, and adeletion 530. In this example, in FIG. 5E, the screenshot editinginterface 520 also includes the screenshot image 534 within an imagearea bounded by cropping interface elements (e.g., crop handles) 532A,532B, 532C, and 532D (sometimes collectively referred to herein as the“cropping interface elements 532”).

In some embodiments, the device (718): detects, via the one or moreinput devices, a first input that corresponds to selection of thedeletion affordance; and, in response to the selection of the deletionaffordance: replaces display of the screenshot editing interface withthe content displayed on the display prior to displaying the screenshotediting interface; and deletes the screenshot image from an imagestorage repository that is accessible via the device. For example, thefirst input corresponds to a tap gesture at a location associated withthe deletion affordance. In another example, the first input correspondsto a mouse click at a location associated with the deletion affordance.In yet another example, the first input corresponds to a predefinedvoice command. In some embodiments, the device deletes the screenshotimage from the camera roll or image/media content library in response tothe selection of the deletion affordance. According to some embodiments,the deletion affordance within the screenshot editing interface providesa seamless user experience that requires less time and user inputs whendeleting screenshot images, which, additionally, reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

For example, with reference to FIG. 5E, in response to activation (e.g.,selection with a contact) of the affordance 530 (e.g., the deletionaffordance), the device 100 causes the modified screenshot image to bedeleted from the image storage repository. Continuing with this example,with reference to FIG. 5E, the device 100 also deletes the unmodifiedscreenshot image and/or modified screenshot images (if any) from theimage storage repository in response to the selection of the affordance530.

In some embodiments, the device (720): detects, via the one or moreinput devices, a second input that corresponds to selection of the doneaffordance; and, in response to the selection of the done affordance:replaces display of the screenshot editing interface with the contentdisplayed on the display prior to displaying the screenshot editinginterface; and, in accordance with a determination that the screenshotimage was modified within the screenshot editing interface, stores amodified screenshot image that corresponds to the screenshot image asmodified within the screenshot editing interface in addition to thescreenshot image in an image storage repository that is accessible viathe device. For example, the second input corresponds to a tap gestureat a location associated with the done affordance. In another example,the second input corresponds to a mouse click at a location associatedwith the done affordance. In yet another example, the second inputcorresponds to a predefined voice command. According to someembodiments, the done affordance within the screenshot editing interfaceprovides a seamless user experience that requires less time and userinputs upon completing modifications to screenshot images, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, the device saves/stores both the unmodifiedscreenshot image(s) and the modified screenshot image saved in the imagestorage repository. In some embodiments, if the screenshot image is notmodified within the screenshot editing interface and the screenshotimage was previously stored in the image storage repository uponcapturing the screenshot image, the screenshot editing interface ceasesto be displayed.

For example, with reference to FIG. 5E, in response to activation (e.g.,selection with a contact) of the affordance 524 (e.g., the doneaffordance), the device 100 replaces display of the screenshot editinginterface 520 with the web browser interface 502 in FIG. 5A. Continuingwith this example, with reference to FIG. 5E, the device 100 alsosaves/stores the modified screenshot image in addition to the unmodifiedscreenshot image in an image storage repository (e.g., the camera rollor image/media content library) in response to the selection of theaffordance 524. In some embodiments, the device 100 periodicallysaves/stores intermediate versions of the modified screenshot image inthe image storage repository prior to detecting selection of theaffordance 524.

In some embodiments, the device (722): detects, via the one or moreinput devices, a request to share the screenshot image; and, in responseto detecting the request to share the screenshot image, displays, on thedisplay, a sharing interface (e.g., a transport interface, or an emailor SMS composition interface) associated with an application by which toshare the screenshot image, where the sharing interface includes thescreenshot image and metadata associated with the screenshot image. Insome embodiments, the request to share to screenshot image correspondsto a user input selecting a share affordance within the screenshotediting interface followed by a subsequent user input selecting anapplication or communication means by which to share the screenshotimage. For example, the user input corresponds to a tap gesture at alocation associated with the sharing affordance. In another example, theuser input corresponds to a mouse click at a location associated withthe sharing affordance. In yet another example, the user inputcorresponds to a predefined voice command. According to someembodiments, the screenshot editing interface provides a seamless userexperience that requires less time and user inputs when sharingscreenshot images, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, intermediate steps associated with display of thesharing affordance includes displaying a sharing options panel (e.g.,the transport interface) with a plurality of sharing options anddetecting selection of a respective sharing option from among theplurality of sharing options that corresponds to the application bywhich to share the screenshot image. In some embodiments, the metadatacorresponds to the time, date, and application associated with thescreenshot image. In some embodiments, the metadata corresponds to a URLor title associated with screenshot image (e.g., when the screenshotimage corresponds to a web page). In some embodiments, the metadatacorresponds to a download link or application store link to theapplication associated with the screenshot image from which to retrieveand/or download the associated application.

As one example, FIGS. 5K-5M show a sequence in which the screenshotimage (e.g., as modified/annotated in FIGS. 5E-5K) is shared via anemail. In this example, the email includes metadata associated with thescreenshot image (e.g., the link 588). As another example, FIGS. 6E-6Gshow a sequence in which the screenshot image (e.g., asmodified/expanded in FIGS. 6D-6E) is shared via a message. As yetanother example, FIGS. 6L-6N show a sequence in which the screenshotimage (e.g., as modified/expanded in FIGS. 6J-6L) is shared via anemail. In this example, the email includes metadata associated with thescreenshot image (e.g., the link 6158).

In some embodiments, the device (724): detects, via the one or moreinput devices, a third input that corresponds to selection of the markupaffordance; in response to the selection of the markup affordance,enters an annotation mode of operation for the screenshot image; and, inresponse to detecting a sequence of user inputs while in the annotationmode of operation for the screenshot image, displays, on the display,annotations to the screenshot image based on the sequence of user inputsand a respective markup tool. For example, the third input correspondsto a tap gesture at a location associated with the markup affordance. Inanother example, the third input corresponds to a mouse click at alocation associated with the markup affordance. In yet another example,the third input corresponds to a predefined voice command. In someembodiments, the sequence of user inputs corresponds to writing,underling, circling, sketching, etc. within the screenshot image with astylus or user touch inputs. According to some embodiments, the markupaffordance within the screenshot editing interface provides a seamlessuser experience that requires less time and user inputs when modifyingscreenshot images, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, intermediate steps include displaying a pluralityof markup tools within the screenshot editing interface and detectingselection of a respective markup tool among the plurality of markuptools. In some embodiments, inputs from a stylus cause the device toannotate the screenshot image without selection of the markupaffordance, but touch inputs do not cause the device to annotate thescreenshot image unless the markup affordance is selected. In someembodiments, the ability to annotate the screenshot image is inactiveuntil the markup affordance is selected.

As one example, FIGS. 5E-5F show a sequence in which a first annotation540 is applied to the screenshot image 534 (e.g., circling the word“Caesar”). As another example, FIGS. 5H-5I show a sequence in which asecond annotation 556 is applied to the screenshot image 534 (e.g.,underling and/or highlighting the word “Germans”).

In some embodiments, in response to detecting a sequence of user inputs,via the one or more input devices, that correspond to annotating thescreenshot image, the device displays (726), on the display, annotationsto the screenshot image based on the sequence of user inputs. In someembodiments, the sequence of user inputs corresponds to writing,underling, circling, sketching, etc. within the screenshot image with astylus implement or user touch inputs. In some embodiments, inputs froma stylus cause the device to annotate the screenshot image withoutselection of the markup affordance, but touch inputs cause the device toannotate the screenshot image without selection of the markupaffordance. According to some embodiments, the ability to annotatescreenshot images within the screenshot editing interface provides aseamless user experience that requires less time and user inputs whenmodifying screenshot images, which, additionally, reduces power usageand improves battery life of the device by enabling the user to use thedevice more quickly and efficiently. As one example, FIGS. 5E-5F show asequence in which a first annotation 540 is applied to the screenshotimage 534 (e.g., circling the word “Caesar”). As another example, FIGS.5H-5I show a sequence in which a second annotation 556 is applied to thescreenshot image 534 (e.g., underling and/or highlighting the word“Germans”).

In some embodiments, the device (728): detects, via the one or moreinput devices, a cropping input associated with the cropping interfaceelements that correspond to removing a portion of the screenshot image;and, in response to detecting the cropping input, displays, on thedisplay, a modified screenshot image within the screenshot editinginterface based on the cropping input, where at least one portion of thescreenshot image has been removed from the modified screenshot image. Insome embodiments, the cropping interface elements correspond tomodifying at least one dimension of the screenshot image. According tosome embodiments, the ability to crop screenshot images within thescreenshot editing interface provides a seamless user experience thatrequires less time and user inputs when modifying screenshot images,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, the size of the at least one portion depends on themagnitude of the cropping input. In some embodiments, the at least oneportion depends on the direction of the cropping input. For example, thecropping input corresponds to a sequence of one or more tap-and-draggestures associated with a cropping handle or edge of the screenshotimage that cause diagonal cropping, vertical cropping, and/or horizontalcropping of the screenshot image.

As one example, FIGS. 5I-5J show a sequence in which a first croppinginput crops out a portion 565A of the screenshot image 534. As a result,the first dimension (e.g., height) of the screenshot image 534 has asecond value 558B that is less than the first value 558A in FIG. 5I. Asanother example, FIGS. 5J-5K show a sequence in which a second croppinginput crops out a portion 565B of the screenshot image 534. As a result,the first dimension (e.g., height) of the screenshot image 534 has athird value 558C that is less than the first value 558A in FIG. 5I andthe second value 558B in FIG. 5J.

In some embodiments, the device (730): identifies one or more contentregions and one or more non-content regions within the screenshot image;detects, via the one or more input devices, a cropping input associatedwith the cropping interface elements that correspond to removing aportion of the screenshot image; and, in response to detecting thecropping input, displays, on the display, a modified screenshot imagewithin the screenshot editing interface based on the cropping input andthe one or more content regions, where at least one portion of thescreenshot image has been removed from the modified screenshot image inorder to exclude at least one of the one or more non-content regions.According to some embodiments, the ability to crop screenshot imagesbased on content and non-content regions provides a seamless userexperience that requires less time and user inputs when modifyingscreenshot images to crop out non-content from screenshot images, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, non-content regions correspond to chrome regions,sidebars, navigation regions/bars, address bars, title bars, toolbars,and/or the like. In some embodiments, content regions correspond toother regions with actual content. In some embodiments, the croppinginterface elements correspond to modifying at least one dimension of thescreenshot image. In some embodiments, the device crops the screenshotimage based on the identified content and non-content regions. Forexample, the device reduces the magnitude of the cropping input that isdetected within a content region in order to crop out a non-contentregion but not a portion of a content region. In another example, thedevice increases the magnitude of the cropping input that is detectedwithin a non-content region in order to crop out an entire non-contentregion.

As one example, FIGS. 5I-5J show a sequence in which a first croppinginput crops out a portion 565A of the screenshot image 534 based on thecontent regions of the screenshot image 534. In this example, the device100 adjusts the cropped-out portion 565A based on the locations of thechrome region (e.g., the display region that includes the indicator(s)402, the time 404, and the battery status indicator 406), the addressbar 506, and the content region 504. As another example, FIGS. 5J-5Kshow a sequence in which a second cropping input crops out a portion565B of the screenshot image 534 based on the content regions of thescreenshot image 534. In this example, the device 100 adjusts thecropped-out portion 565B based on the locations of the content region504 and the toolbar region that includes the affordances 510A, 510B,512A, 512B, and 512C.

In some embodiments, the device (732): identifies a first regionassociated with a first application and a second region associated witha second application within the screenshot image; detects, via the oneor more input devices, a cropping input associated with the croppinginterface elements that correspond to removing a portion of thescreenshot image; and, in response to detecting the cropping input,displays, on the display, a modified screenshot image within thescreenshot editing interface based on the cropping input and the firstand second regions, where at least one portion of the screenshot imagehas been removed from the modified screenshot image in order to excludeone of the first region or the second region. In some embodiments, thecaptured screenshot image includes a multitasking or split-screen viewwith a first sub-portion of the content within the first region for thefirst application and a second sub-portion of the content within thesecond region for the second application. According to some embodiments,the ability to crop screenshot images based on application regionsprovides a seamless user experience that requires less time and userinputs when modifying screenshot images to crop out portions of asplit-screen view from screenshot images, which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some embodiments, the device crops the screenshot image based on theidentified first and second regions. For example, the device reduces themagnitude of the cropping input that is detected within a second regionin order to crop out the first region but not a portion of the secondregion. In another example, the device increases the magnitude of thecropping input that is detected within the first region in order to cropout the entire first region.

As one example, in FIG. 5Y, the device 100 displays a split-screen userinterface that includes a first region associated with a web browserinterface 5100 and a second region associated with a messaging interface5150. In this example, FIGS. 5BB-5CC show a sequence in which a croppinginput crops out the second region of the screenshot image 534 based onthe identified first and second content regions of the screenshot image5168. In this example, the device 100 adjusts the cropped version of thescreenshot image 5168 based on the divider element 5149 and the firstand second regions of the split-screen user interface.

In some embodiments, the device (734): prior to detecting the respectiveinput directed to the thumbnail representation of the screenshot image,detecting, via the one or more input devices, a subsequent screenshotcapture input; and, in response to detecting the subsequent screenshotcapture input: captures a second screenshot image of content displayedon the display; and displays, on the display, a group of thumbnailrepresentations that represents a first thumbnail representationcorresponding to the screenshot image and the second thumbnailrepresentation corresponding to the second screenshot image. In someembodiments, the subsequent screenshot input corresponds to a keypress(e.g., print screen key) or a keypress combination (e.g., homebutton+power button). In some embodiments, the subsequent screenshotinput corresponds to selection of an associated affordance (e.g.,through a sharing panel or transport interface).

In some embodiments, the subsequent screenshot capture input is detectedprior to expiration of the timeout period, else the previous thumbnailrepresentation is removed from the display and the associated screenshotimage is removed from the camera roll and the subsequent screenshotimage is not part of a batch but a standalone screenshot image. In someembodiments, detection of the subsequent screenshot capture input resetsthe timeout period. As such, the user has the option to add additionalscreenshots to the group.

For example, the group of thumbnail representations corresponds to astack of thumbnail representations. In some embodiments, the user isable to select the group of thumbnail representations for editing ordismissing the group of thumbnail representations using analogousgestures to those described above (e.g., a tap on the group of thumbnailrepresentations opens the screenshot editing interface for editing thegroup of screenshot images, a swipe on the group of thumbnailrepresentations to dismiss the group of thumbnail representations,etc.).

In some embodiments, the device saves/stores subsequent screenshot imagein the image storage repository. In some embodiments, the subsequentscreenshot image includes different content due to a navigation command(e.g., scrolling) that changes the content displayed on the display ascompared to the content captured within the previous screenshot image.According to some embodiments, the ability to perform a batchedscreenshot capture operation provides a seamless user experience thatrequires less time and user inputs when viewing and modifying multiplescreenshot images, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

As one example, FIGS. 5P-5U show a sequence in which a group ofthumbnail representations of screenshot images are overlaid on the webbrowser interface in response to multiple screenshot capture inputs. Inthis example, with reference to FIG. 5U, the device 100 displays a groupof thumbnail representations 5120, 5124, and 5128 overlaid on the webbrowser interface 5100.

In some embodiments, the respective input is directed to (736) the groupof thumbnail representations, and the screenshot editing interfaceincludes the second screenshot image. In some embodiments, thescreenshot editing interface optionally includes at least a portion ofthe previous screenshot image. In some embodiments, the screenshotediting interface for batched screenshots includes the most recentscreenshot image and a peak of at least the second most recentscreenshot image to indicate that multiple screenshot images areavailable for editing within the screenshot editing interface. Accordingto some embodiments, the screenshot editing interface associated withthe batched screenshot capture operation provides a seamless userexperience that requires less time and user inputs when viewing andmodifying multiple screenshot images, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

As one example, in FIG. 5U, the device 100 detects a contact 5130 (e.g.,a tap/selection gesture) at a location that corresponds to the group ofthumbnail representations 5120, 5124, and 5128. Continuing with thisexample, in FIG. 5V, in FIG. 5U, the device 100 replaces display of theweb browser interface 5100 with a screenshot editing interface 520 inresponse to the selection of the group of thumbnail representations5120, 5124, and 5128 in FIG. 5U. As shown in FIG. 5V, the screenshotediting interface 520 includes the third screenshot image 5132 (e.g.,associated with the third thumbnail representation 5128 in FIG. 5U)within an image area bounded by cropping interface elements 532 (e.g.,crop handles). As shown in FIG. 5V, the screenshot editing interface 520includes a portion of the second screenshot image 5134 (e.g., associatedwith the second thumbnail representation 5124 in FIGS. 5S-5T). Accordingto some embodiments, the user is able to individually modify the thirdscreenshot image 5132, the second screenshot image 5134, and the firstscreenshot image 5136 within the screenshot editing interface 520.According to some embodiments, the user is able to navigate between thethird screenshot image 5132, the second screenshot image 5134, and thefirst screenshot image 5136 within the screenshot editing interface 520(e.g., with a swipe gesture as shown in FIGS. 5V-5W).

In some embodiments, the device (738): detects, via the one or moreinput devices, a navigation input that corresponds to navigating amongscreenshot images in the screenshot editing interface; and, in responseto detecting the navigation input, updates the screenshot editinginterface by displaying the screenshot image. In some embodiments, thenavigation input corresponds to a scrolling gesture such as moving ascroll bar or a swipe gesture. In some embodiments, the screenshotediting interface optionally includes at least a portion of the secondscreenshot image. According to some embodiments, the user is able toquickly navigate between the batched screenshot images. In someembodiments, the batched screenshot images are separately editable suchthat a user has the option to individually crop, annotate, etc. one ormore of the screenshot images within the screenshot editing interface.According to some embodiments, the ability to navigate between multiplescreenshot images within the screenshot editing interface associatedwith the batched screenshot capture operation provides a seamless userexperience that requires less time and user inputs when viewing andmodifying multiple screenshot images, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

As one example, in FIG. 5V, the device 100 detects a navigation gesturewith a contact 5138 (e.g., a right-to-left swipe or tap-and-draggesture) within the screenshot editing interface 520. Continuing withthis example, in FIG. 5W, in FIG. 5V, the device 100 updates thescreenshot editing interface 520 to show the second screenshot image5134 (e.g., associated with the second thumbnail representation 5124 inFIGS. 5S-5T) within an image area bounded by cropping interface elements532 (e.g., crop handles). As shown in FIG. 5W, the screenshot editinginterface 520 also includes a portion of the third screenshot image 5132(e.g., associated with the third thumbnail representation 5128 in FIG.5U) and a portion of the first screenshot image 5136 (e.g., associatedwith the first thumbnail representation 5120 in FIGS. 5Q-5R).

In some embodiments, the content is displayed (740) within anapplication window, and the device: detects, via the one or more inputdevices, a sequence of inputs that corresponds to dragging and droppingthe thumbnail representation into the application window; and, inresponse to detecting the sequence of user inputs, displays, on thedisplay, the screenshot image within the application window. As oneexample, the application window corresponds to an email application andthe screenshot image corresponds to the email application. In thisexample, the thumbnail representation is dragged from its originlocation into the email application, and, as a result, the screenshotimage is displayed within the body of an email being composed within theemail application. For example, with reference to FIG. 6I, in responseto a user input dragging-and-dropping the thumbnail representation 6106of the screenshot image 6110 into the message input field 6104, thedevice 100 would populate the message input field 6104 with thescreenshot image 6110 (or a thumbnail thereof) in order to send thescreenshot image 6110 in a new message. According to some embodiments,the ability to perform a drag-and-drop operation on the thumbnailrepresentation of a screenshot image provides a seamless user experiencethat requires less time and user inputs when inserting/exporting thescreenshot image into an application, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

In some embodiments, the content includes (742) a first contentsub-portion displayed within a first region associated with a firstapplication and a second content sub-portion displayed within a secondregion associated with a second application, and the device: detects,via the one or more input devices, a sequence of inputs that correspondsto dragging and dropping the thumbnail representation into the firstregion; and, in response to detecting the sequence of user inputs,displays, on the display, the screenshot image within the first region.As one example, the content is displayed in a multitasking orsplit-screen view where the first region corresponds to a firstapplication window for the first application (e.g., a messagingapplication) and the second region corresponds to a second applicationwindow for the second application (e.g., a web browser application.Alternatively, the thumbnail representation is dragged and dropped intothe second region. As one example, FIGS. 5Z-5AA show a sequence in whichthe thumbnail representation of the screenshot image isdragged-and-dropped into one of the regions of the split-screen userinterface. According to some embodiments, the ability to perform adrag-and-drop operation on the thumbnail representation of a screenshotimage provides a seamless user experience that requires less time anduser inputs when inserting/exporting the screenshot image into anapplication, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, in response to detecting the respective inputdirected to the thumbnail representation of the screenshot image, and inaccordance with a determination that the respective input corresponds toa request to cease to display the thumbnail representation, the device(744) ceases to display the thumbnail representation of the screenshotimage overlaid on the content displayed on the display. In someembodiments, the request to cease to display the thumbnailrepresentation (e.g., the second type of input) corresponds to aleft-to-right or right-to-left swipe gesture starting at a locationassociated with the thumbnail representation that swipes the thumbnailrepresentation off of the display. In some embodiments, the request tocease to display the thumbnail representation corresponds todragging-and-dropping the thumbnail representation to a deletion/removalregion. According to some embodiments, the ability to quickly dismissthe thumbnail representation of a screenshot image provides a seamlessuser experience that requires less time and user inputs, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, in response to detecting the respective input, andin accordance with a determination that the respective input correspondsto a request to cease to display the thumbnail representation, thedevice also deletes the screenshot image from the camera roll. As oneexample, FIGS. 5N-5O show a sequence in which the thumbnailrepresentation of the screenshot image ceases to be displayed over theweb browser interface.

In some embodiments, the device (746): after handling the screenshotimage (e.g., editing or dismissing the first screenshot image), detects,via the one or more input devices, a subsequent screenshot captureinput; in response to detecting the subsequent screenshot capture input:captures a second screenshot image of the content displayed on thedisplay; and displays, on the display, a second thumbnail representationof the second screenshot image overlaid on the content displayed on thedisplay and captured within the screenshot image; and, in accordancewith a determination that the timeout period has expired (and no inputhas been detected that is directed to the thumbnail representation),ceases to display the second thumbnail representation of the secondscreenshot image overlaid on the content displayed on the display. Forexample, the timeout period corresponds to an X seconds timer. In someembodiments, the second screenshot image is also deleted from the cameraroll. According to some embodiments, expiration of the timeout periodindicates disinterest in the screenshot image and causes dismissal ofthe thumbnail representation of the screenshot image in order to providea seamless and non-intrusive user experience that requires less time anduser inputs, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the subsequent screenshot input corresponds to akeypress (e.g., print screen key) or a keypress combination (e.g., homebutton+power button). In some embodiments, the subsequent screenshotinput corresponds to selection of an associated affordance (e.g.,through a sharing panel or transport interface). In some embodiments,the screenshot image is saved in the camera roll. In some embodiments,the screenshot image includes the entire display area of the device. Insome embodiments, the screenshot image includes a portion of the displayarea of the device (e.g., including application related content butexcluding OS related content such as an OS chrome bar).

It should be understood that the particular order in which theoperations in FIGS. 7A-7E have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,the method 800) are also applicable in an analogous manner to method 700described above with respect to FIGS. 7A-7E. For example, the screenshotcapture inputs, screenshot thumbnail representations, screenshot images,and screenshot editing interface described above with reference tomethod 700 optionally have one or more of the characteristics of thescreenshot capture inputs, screenshot thumbnail representations,screenshot images, and screenshot editing interface described hereinwith reference to other methods described herein (e.g., the method 800).For brevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A, 3, and 5A) orapplication specific chips. Further, the operations described above withreference to FIGS. 7A-7E, optionally, implemented by components depictedin FIGS. 1A-1B. For example, the screenshot capture inputs, croppinginputs, and navigation inputs are, optionally, implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive surface604, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

FIGS. 8A-8C illustrate a flow diagram of a method 800 of expanding ascreenshot image in accordance with some embodiments. The method 800 isperformed at an electronic device (e.g., the portable multifunctiondevice 100 in FIG. 1A, or the device 300 in FIG. 3) with one or moreprocessors, non-transitory memory, a display, and one or more inputdevices. In some embodiments, the display is a touch-screen display andthe one or more input devices are on or integrated with the display(e.g., the device is a tablet or smartphone). In some embodiments, thedisplay is separate from the one or more input devices (e.g., the deviceis a laptop with a separate display and touchpad, or desktop computerwith a separate display and mouse). Some operations in method 800 are,optionally, combined and/or the order of some operations is, optionally,changed.

As described below, the method 800 provides an intuitive way to expand ascreenshot image. The method reduces the cognitive burden on a user whenexpanding a screenshot image, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,enabling a user to expand a screenshot image faster and more efficientlyconserves power and increases the time between battery charges.

The device displays (802), on the display, a first sub-portion ofcontent within an application interface. For example, the sub-portion ofthe content corresponds to a first page of a multi-page web article or afirst portion of a scrollable web page displayed within a web browserapplication. In another example, the sub-portion of the contentcorresponds to a first page or a first portion of a PDF displayed in aweb browser application or a PDF viewer application. In yet anotherexample, the sub-portion of the content corresponds to a subset of aplurality of messages (e.g., a portion of a message thread or aconversation) displayed within a messaging application or an emailapplication. In yet another example, the sub-portion of the contentcorresponds to a portion of a spreadsheet displayed within a spreadsheetapplication. In yet another example, the sub-portion of the contentcorresponds to a portion of a word processing document displayed withina word processing application.

As one example, in FIG. 6A, the device 100 displays a web browserinterface 600 associated with a web browser application executed by thedevice 100 that includes a content region 607 with a first portion ofthe content 610 for the tab 606-A (e.g., associated with the URL 608).As another example, in FIG. 6H, the device displays a messaginginterface 6100 associated with a messaging application (e.g., instantmessaging, text messaging, etc.) executed by the device 100. In thisexample, the messaging interface 6100 includes a plurality of messages6102A, 6102B, 6102C, 6102D, 6102E, 6102F, 6102G, and 6102H.

While displaying the first sub-portion of the content, the devicedetects (804), via the one or more input devices, a screenshot captureinput. In some embodiments, the screenshot input corresponds to akeypress (e.g., print screen key) or a keypress combination (e.g., homebutton+power button). In some embodiments, the screenshot inputcorresponds to selection of an associated affordance (e.g., through asharing panel or transport interface). As one example, in FIG. 6B, thescreenshot capture input corresponds to selection of the operationaffordance 656E with the contact 637 (e.g., with a tap/selection input).

In response to detecting the screenshot capture input, the device (806):captures a screenshot image of the first sub-portion of the contentwithin the application interface; and displays, on the display, ascreenshot editing interface provided to edit the screenshot image,where the screenshot editing interface includes the screenshot image ofthe first sub-portion of the content within an image area and one ormore expansion affordances provided to expand the screenshot image in acorresponding direction. In some embodiments, the device replacesdisplay of the application interface with the screenshot editinginterface. In some embodiments, the screenshot editing interface isoverlaid on the application interface. In some embodiments, the devicestores/saves the screenshot image in an image storage repository (e.g.,the camera roll or image/media content library). In some embodiments,the screenshot image includes the entire display area of the device. Insome embodiments, the screenshot image includes a portion of the displayarea of the device (e.g., including application related content butexcluding OS related content such as an OS chrome bar). According tosome embodiments, the screenshot editing interface provides a seamlessuser experience that requires less time and user inputs when expandingscreenshot images, which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, the one or more expansion affordances are providedto expand the content in a vertical dimension (e.g., height) eitherupward or downward. In some embodiments, the one or more expansionaffordances are provided to expand the content in a horizontal dimension(e.g., width) either left or right. In some embodiments, the one or moreexpansion affordances are provided to expand the content in twodimensions diagonally. In some embodiments, the device displays the oneor more expansion affordances proximate to the perimeter of the imagearea such as proximate to each corner of the image area.

As one example, in FIG. 6D, the screenshot editing interface 620includes the screenshot image 640 within an image area bounded bycropping interface elements 632 (e.g., crop handles). In this example,in FIG. 6D, a first portion 642 of the content associated with the URL608 (e.g., content that was displayed within the web browser interface600 in FIG. 6A) is displayed within the image area bounded by thecropping interface elements 632. As another example, in FIG. 6J, thescreenshot editing interface 620 includes the screenshot image 6110within an image area bounded by cropping interface elements 632 (e.g.,crop handles). In this example, in FIG. 6J, a first portion 6112 of themessaging content associated with messages 6102A, 6102B, 6102C, 6102D,6102E, 6102F, 6102G, and 6102H (e.g., content that was displayed withinthe messaging interface 610 in FIG. 6H) is displayed within the imagearea bounded by the cropping interface elements 632.

In some embodiments, displaying the screenshot editing interfaceincludes (808) displaying the second sub-portion of the content outsideof the image area prior to detecting the expansion input. In someembodiments, one or more additional sub-portions of the content aredisplayed within the screenshot editing interface for expanding thescreenshot image in one or more directions and/or one or moredimensions. For example, the device displays an additional pre-fetchedcontent above and below the first sub-portion within the screenshotediting interface. In this example, the additional pre-fetched contentis associated with a predefined length in lines or size in pixels.According to some embodiments, the display of the second sub-portion ofthe content outside of the image area provides a visual cue indicatingthat the screenshot image may be expanded to include the secondsub-portion.

As one example, in FIG. 6D, a second portion 644 of the contentassociated with the URL 608 (e.g., content that was not displayed withinthe web browser interface 600 in FIG. 6A) is displayed outside of theimage area bounded by the cropping interface elements 632. As anotherexample, in FIG. 6J, a second portion 6114 of the messaging contentassociated with messages 6102I, 6102J, and 6102K (e.g., content that wasnot displayed within the messaging interface 610 in FIG. 6H) isdisplayed outside of the image area bounded by the cropping interfaceelements 632.

While displaying the screenshot editing interface, the device detects(810), via the one or more input devices, an expansion input thatcorresponds to expanding the screenshot image in one or more dimensions.As one example, in FIG. 6D, the device 100 detects an expansion input ina downward direction from a bottom edge of the screenshot image 640 witha contact 636 (e.g., a tap-and-drag gesture). As another example, inFIG. 6J, the device 100 detects an expansion input in an upwarddirection from a top edge of the screenshot image 6110 with a contact6122 (e.g., a tap-and-drag gesture).

In some embodiments, the expansion input corresponds to (812) a verticalexpansion of the screenshot image in order to expand a verticaldimension of the screenshot image. As one example, FIGS. 6D-6E show asequence in which an expansion input expands the screenshot image 640vertically to include both the first portion 642 and the second portion644 within the image area bounded by cropping interface elements 632. Asanother example, FIGS. 6J-6L show a sequence in which an expansion inputexpands the screenshot image 6110 vertically to include both the firstportion 6112 and the second portion 6114 within the image area boundedby cropping interface elements 632.

In some embodiments, the expansion input corresponds to (814) ahorizontal expansion of the screenshot image in order to expand ahorizontal dimension of the screenshot image. As one example, ascreenshot image associated with a spreadsheet interface has the optionbe expanded in a horizontal direction to include additional columns orin a vertical direction to include additional rows in response to a userinput.

In some embodiments, the expansion input corresponds to (816) a diagonalexpansion of the screenshot image in order to expand two dimensions ofthe screenshot image. As one example, a screenshot image associated witha spreadsheet interface has the option to be expanded in a diagonaldirection to include additional columns and additional rows in responseto a user input.

In response to detecting the expansion input, the device modifies (818)the screenshot image by displaying a second sub-portion of the contentwithin the image area in addition to the first sub-portion of thecontent (e.g., appended or prepended to the first sub-portion of thecontent), where the second sub-portion of the content was not displayedwithin the application interface before detecting the screenshot captureinput. According to some embodiments, the ability to expand screenshotimages within the screenshot editing interface provides a seamless userexperience that requires less time and user inputs, which, additionally,reduces power usage and improves battery life of the device by enablingthe user to use the device more quickly and efficiently.

As one example, FIGS. 6D-6E show a sequence in which an expansion inputexpands the screenshot image 640 to include both the first portion 642and the second portion 644 within the image area bounded by croppinginterface elements 632. In this example, prior to detecting theexpansion input, the device 100 did not display the second portion 644within the web browser interface 600 in FIG. 6A. As another example,FIGS. 6J-6L show a sequence in which an expansion input expands thescreenshot image 6110 to include both the first portion 6112 and thesecond portion 6114 within the image area bounded by cropping interfaceelements 632. In this example, prior to detecting the expansion input,the device 100 did not display the second portion 6114 within themessaging interface 610 in FIG. 6H.

In some embodiments, in response to detecting the expansion input, thedevice stores (820) the modified screenshot image that includes thefirst and second sub-portions of the content in an image storagerepository that is accessible via the device in addition to thescreenshot image that includes the first sub-portion of the content. Forexample, the device stores the modified screenshot image in the imagestorage repository such as the camera roll or image/media contentlibrary. In some embodiments, at least one dimension of the modifiedscreenshot image is larger than a corresponding dimension of the display(e.g., the modified screenshot image has a height or width that islarger than the height or width of the display). According to someembodiments, the saving/storing the expanded/modified screenshot imageprovides a seamless user experience that requires less time and userinputs, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

As one example, FIGS. 6D-6E show a sequence in which an expansion inputexpands the screenshot image 640 to include both the first portion 642and the second portion 644 within the image area bounded by croppinginterface elements 632. In this example, the device 100 stores/saves theexpanded screenshot image 640 that includes the first portion 642 andthe second portion 644 in FIG. 6E in the camera roll or image/mediacontent library in addition to the unexpanded screenshot image thatincludes the first portion 642 in FIG. 6D.

In some embodiments, the second sub-portion is determined (822) based ona direction of the expansion input. In some embodiments, the secondsub-portion corresponds to content proximate to the first sub-portionbased on the directionality of the expansion input. For example, inaccordance with a determination that the expansion input indicates afirst direction of expansion, the second sub-portion is a sub-portion ofthe content that precedes the first sub-portion. In another example, inaccordance with a determination that the expansion input indicates asecond direction of expansion, the second sub-portion is a sub-portionof the content that follows the first sub-portion. According to someembodiments, the ability to expand screenshot images based on thedirectionality of the expansion input provides a seamless userexperience that requires less time and user inputs when expandingscreenshot images within the screenshot editing interface, which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, a size of the second sub-portion is determined(824) based on a magnitude of the expansion input. In some embodiments,the second sub-portion corresponds to content proximate to the firstsub-portion based on the magnitude of the expansion input. For example,in accordance with a determination that the expansion input has a firstmagnitude, the second sub-portion has a first size. In another example,in accordance with a determination that the expansion input has a secondmagnitude that is greater than the first magnitude, the secondsub-portion has a second size that is greater than the first size). Insome embodiments, the magnitude is based on the duration of the input.In some embodiments, the magnitude is based on a distance of movement ofthe input. In some embodiments, the magnitude is based on a speed ofmovement of the input. According to some embodiments, the ability toexpand screenshot images based on the magnitude of the expansion inputprovides a seamless user experience that requires less time and userinputs when expanding screenshot images within the screenshot editinginterface, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some embodiments, modifying the screenshot image includes (826)scrolling at least a portion of the image area in order to maintain adimension of the screenshot image. For example, if the screenshot imageis expanded vertically, the device maintains the width dimension of thescreenshot image and scrolls a portion of the first sub-portion off ofthe display area. According to some embodiments, scrolling theexpanded/modified screenshot image to maintain one or more dimension ofthe screenshot image provides a seamless and intuitive user experiencewhen expanding screenshot images within the screenshot editinginterface, which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

As one example, FIGS. 6D-6E show a sequence in which an expansion inputexpands the screenshot image 640 to include both the first portion 642and the second portion 644 within the image area bounded by croppinginterface elements 632. In this example, in FIG. 6E, the screenshotediting interface 620 includes a “scroll to see more” indicator 648 toalert the user than a portion of the screenshot image has been scrolledand may be viewed in response to detecting a scroll input within thescreenshot interface 620 (e.g., a voice command, or an upward ordownward swipe gesture over the screenshot image 640). As shown in FIG.6E, the dimensions of the screenshot image 640 are maintained betweenFIGS. 6D and 6E. As such, the device appends the second portion 644 ofthe content associated with the URL 608 to the first portion 642 of thecontent associated with the URL 608 and scrolls the screenshot image.

In some embodiments, modifying the screenshot image includes (828)shrinking the screenshot image in order to concurrently display thefirst and second sub-portions of the content within the image area. Forexample, if the screenshot image is expanded vertically, the deviceshrinks the first and second sub-portions so that the first sub-portionand the second sub-portion are concurrently displayed within thescreenshot editing interface. According to some embodiments, shrinkingthe screenshot image to display the entirety of the expanded/modifiedscreenshot image provides a seamless and intuitive user experience whenexpanding screenshot images within the screenshot editing interface,which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

As another example, FIGS. 6J-6L show a sequence in which an expansioninput expands the screenshot image 6110 to include both the firstportion 6112 and the second portion 6114 within the image area boundedby cropping interface elements 632. In this example, in FIG. 6L, thedevice 100 shrinks the dimensions of the screenshot image 6110 betweenFIGS. 6J-6L to display the entirety of the expanded screenshot image.

In some embodiments, the second sub-portion of the content is rendered(830) by an application associated with the content and subsequentlydisplayed within the screenshot editing interface. In some embodiments,the device 100 pre-fetches one or more additional sub-portions of thecontent for display within the screenshot editing interface. As oneexample, with reference to FIG. 6D, the second portion 644 of thecontent associated with the URL 608 is pre-fetched by the web browserapplication. As another example, with reference to FIG. 6J, the secondportion 6114 of the messaging content associated with messages 6102I,6102J, and 6102K is pre-fetched by the messaging application.

In some embodiments, the device (832): detects, via the one or moreinput devices, a subsequent expansion input that corresponds toexpanding the screenshot image in one or more dimensions; and, inresponse to detecting the subsequent expansion input, modifies thescreenshot image by displaying a third sub-portion of the content withinthe image area in addition to the first and second sub-portions of thecontent (e.g., appended or prepended to the first sub-portion of thecontent), where the third sub-portion of the content was not displayedbefore detecting the screenshot capture input. According to someembodiments, the ability to further expand screenshot images within thescreenshot editing interface provides a seamless user experience thatrequires less time and user inputs, which, additionally, reduces powerusage and improves battery life of the device by enabling the user touse the device more quickly and efficiently.

As one example, with reference to FIG. 6E, in response to detecting asubsequent expansion input in a downward direction from the bottom edgeof the screenshot image 640, the device 100 would expand the screenshotimage to include the third portion 646 (or at least a portion thereof)within the image area bounded by cropping interface elements 632 inaddition to the fist portion 642 and the second portion 644.

It should be understood that the particular order in which theoperations in FIGS. 8A-8C have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,the method 700) are also applicable in an analogous manner to method 800described above with respect to FIGS. 8A-8C. For example, the screenshotcapture inputs and expansion inputs described above with reference tomethod 800 optionally have one or more of the characteristics of thescreenshot capture inputs and expansion inputs described herein withreference to other methods described herein (e.g., the method 700). Forbrevity, these details are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A, 3, and 5A) orapplication specific chips. Further, the operations described above withreference to FIGS. 8A-8C, optionally, implemented by components depictedin FIGS. 1A-1B. For example, the screenshot capture inputs and expansioninputs are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive surface 604, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method comprising: at a device with one or moreprocessors, non-transitory memory, a display, and one or more inputdevices: while displaying content on the display, detecting, via the oneor more input devices, a screenshot input; in response to detecting thescreenshot input: capturing a first screenshot of at least a portion ofthe content; and displaying a representation of the first screenshot onthe display; detecting, via the one or more input devices, a selectioninput directed to the representation of the first screenshot; inresponse to detecting the selection input directed to the representationof the first screenshot and in accordance with a determination that therepresentation of the first screenshot corresponds to multiplescreenshots, displaying, on the display, a screenshot editing userinterface for editing the multiple screenshots; and while in thescreenshot editing interface for editing the multiple screenshots:displaying a representation of the first screenshot; while displayingthe representation of the first screenshot, detecting, via the one ormore input devices, a navigation input; and in response to detecting thenavigation input, replacing at least a portion of the representation ofthe first screenshot with a representation of a second screenshot. 2.The method of claim 1, further comprising: in response to detecting theselection input directed to the representation of the first screenshotand in accordance with a determination that the representation of thefirst screenshot corresponds to a single screenshot, displaying, on thedisplay, a screenshot editing user interface for editing the singlescreenshot.
 3. The method of claim 1, wherein the screenshot editinginterface for editing the multiple screenshots includes a representationof the first screenshot and at least a portion of a representation ofthe second screenshot.
 4. The method of claim 1, wherein the screenshotediting interface for editing the multiple screenshots includes anaffordance for performing an operation associated with the multiplescreenshots.
 5. The method of claim 1, wherein the screenshot editinginterface for editing the multiple screenshots includes an affordancefor performing an operation associated with one screenshot but not otherscreenshots.
 6. The method of claim 1, wherein the screenshot editinginterface for editing the multiple screenshots includes one or moreediting affordances, and the method further comprising: in response todetecting the navigation input, maintaining display of the one or moreediting controls when while replacing at least the portion of therepresentation of the first screenshot with the representation of asecond screenshot.
 7. The method of claim 1, wherein the representationof the first screenshot corresponds to a thumbnail of the firstscreenshot.
 8. The method of claim 1, wherein the representation of thefirst screenshot corresponds to a representation of a stack ofscreenshots according to a determination that multiple screenshots havebeen captured.
 9. The method of claim 1, wherein the representation ofthe first screenshot includes a representation of at least a portion ofa second screenshot according to a determination that multiplescreenshots have been captured.
 10. An electronic device comprising: oneor more processors; non-transitory memory; a display; one or more inputdevices; and one or more programs, wherein the one or more programs arestored in the non-transitory memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: while displaying content on the display, detect, via the one ormore input devices, a screenshot input; in response to detect thescreenshot input: capture a first screenshot of at least a portion ofthe content; and display a representation of the first screenshot on thedisplay; detect, via the one or more input devices, a selection inputdirected to the representation of the first screenshot; in response todetecting the selection input directed to the representation of thefirst screenshot and in accordance with a determination that therepresentation of the first screenshot corresponds to multiplescreenshots, display, on the display, a screenshot editing userinterface for editing the multiple screenshots; and while in thescreenshot editing interface for editing the multiple screenshots:display a representation of the first screenshot; while displaying therepresentation of the first screenshot, detect, via the one or moreinput devices, a navigation input; and in response to detecting thenavigation input, replace at least a portion of the representation ofthe first screenshot with a representation of a second screenshot. 11.The electronic device of claim 10, wherein the one or more programsfurther include instructions for: in response to detecting the selectioninput directed to the representation of the first screenshot and inaccordance with a determination that the representation of the firstscreenshot corresponds to a single screenshot, display, on the display,a screenshot editing user interface for editing the single screenshot.12. The electronic device of claim 10, wherein the screenshot editinginterface for editing the multiple screenshots includes a representationof the first screenshot and at least a portion of a representation ofthe second screenshot.
 13. The electronic device of claim 10, whereinthe representation of the first screenshot corresponds to a thumbnail ofthe first screenshot.
 14. The electronic device of claim 10, wherein therepresentation of the first screenshot corresponds to a representationof a stack of screenshots according to a determination that multiplescreenshots have been captured.
 15. The electronic device of claim 10,wherein the representation of the first screenshot includes arepresentation of at least a portion of a second screenshot according toa determination that multiple screenshots have been captured.
 16. Anon-transitory computer readable storage medium storing one or moreprograms, the one or more programs comprising instructions, which, whenexecuted by an electronic device with a display and one or more inputdevices, cause the electronic device to: while displaying content on thedisplay, detect, via the one or more input devices, a screenshot input;in response to detect the screenshot input: capture a first screenshotof at least a portion of the content; and display a representation ofthe first screenshot on the display; detect, via the one or more inputdevices, a selection input directed to the representation of the firstscreenshot; in response to detecting the selection input directed to therepresentation of the first screenshot and in accordance with adetermination that the representation of the first screenshotcorresponds to multiple screenshots, display, on the display, ascreenshot editing user interface for editing the multiple screenshots;and while in the screenshot editing interface for editing the multiplescreenshots: display a representation of the first screenshot; whiledisplaying the representation of the first screenshot, detect, via theone or more input devices, a navigation input; and in response todetecting the navigation input, replace at least a portion of therepresentation of the first screenshot with a representation of a secondscreenshot.
 17. The non-transitory computer readable storage medium ofclaim 16, wherein the one or more programs further comprise instructionsfor: in response to detecting the selection input directed to therepresentation of the first screenshot and in accordance with adetermination that the representation of the first screenshotcorresponds to a single screenshot, display, on the display, ascreenshot editing user interface for editing the single screenshot. 18.The non-transitory computer readable storage medium of claim 16, whereinthe screenshot editing interface for editing the multiple screenshotsincludes a representation of the first screenshot and at least a portionof a representation of the second screenshot.
 19. The non-transitorycomputer readable storage medium of claim 16, wherein the representationof the first screenshot corresponds to a thumbnail of the firstscreenshot.
 20. The non-transitory computer readable storage medium ofclaim 16, wherein the representation of the first screenshot correspondsto a representation of a stack of screenshots according to adetermination that multiple screenshots have been captured.
 21. Thenon-transitory computer readable storage medium of claim 16, wherein therepresentation of the first screenshot includes a representation of atleast a portion of a second screenshot according to a determination thatmultiple screenshots have been captured.